Initial commit

This commit is contained in:
Zhongwei Li
2025-11-30 08:28:02 +08:00
commit f60eb4547f
4 changed files with 110 additions and 0 deletions

View File

@@ -0,0 +1,11 @@
{
"name": "dev-docs",
"description": "Command set for developer docs lookup and updates",
"version": "0.1.0",
"author": {
"name": "ClaudeSmith"
},
"commands": [
"./commands"
]
}

3
README.md Normal file
View File

@@ -0,0 +1,3 @@
# dev-docs
Command set for developer docs lookup and updates

51
commands/dev-docs.md Normal file
View File

@@ -0,0 +1,51 @@
---
description: Create a comprehensive strategic plan with structured task breakdown
argument-hint: Describe what you need planned (e.g., "refactor authentication system", "implement microservices")
---
You are an elite strategic planning specialist. Create a comprehensive, actionable plan for: $ARGUMENTS
## Instructions
1. **Analyze the request** and determine the scope of planning needed
2. **Examine relevant files** in the codebase to understand current state
3. **Create a structured plan** with:
- Executive Summary
- Current State Analysis
- Proposed Future State
- Implementation Phases (broken into sections)
- Detailed Tasks (actionable items with clear acceptance criteria)
- Risk Assessment and Mitigation Strategies
- Success Metrics
- Required Resources and Dependencies
- Timeline Estimates
4. **Task Breakdown Structure**:
- Each major section represents a phase or component
- Number and prioritize tasks within sections
- Include clear acceptance criteria for each task
- Specify dependencies between tasks
- Estimate effort levels (S/M/L/XL)
5. **Create task management structure**:
- Create directory: `dev/active/[task-name]/` (relative to project root)
- Generate three files:
- `[task-name]-plan.md` - The comprehensive plan
- `[task-name]-context.md` - Key files, decisions, dependencies
- `[task-name]-tasks.md` - Checklist format for tracking progress
- Include "Last Updated: YYYY-MM-DD" in each file
## Quality Standards
- Plans must be self-contained with all necessary context
- Use clear, actionable language
- Include specific technical details where relevant
- Consider both technical and business perspectives
- Account for potential risks and edge cases
## Context References
- Check `PROJECT_KNOWLEDGE.md` for architecture overview (if exists)
- Consult `BEST_PRACTICES.md` for coding standards (if exists)
- Reference `TROUBLESHOOTING.md` for common issues to avoid (if exists)
- Use `dev/README.md` for task management guidelines (if exists)
**Note**: This command is ideal to use AFTER exiting plan mode when you have a clear vision of what needs to be done. It will create the persistent task structure that survives context resets.

45
plugin.lock.json Normal file
View File

@@ -0,0 +1,45 @@
{
"$schema": "internal://schemas/plugin.lock.v1.json",
"pluginId": "gh:JNLei/claude-tools:plugins/commands/dev-docs",
"normalized": {
"repo": null,
"ref": "refs/tags/v20251128.0",
"commit": "74904c552ca9c1fd8c19ac19cfa3e8b7dd0952d3",
"treeHash": "d576cb4e57504e3555892fead8ab3c20efbf012caf5ce8955345b693c7320147",
"generatedAt": "2025-11-28T10:11:43.521681Z",
"toolVersion": "publish_plugins.py@0.2.0"
},
"origin": {
"remote": "git@github.com:zhongweili/42plugin-data.git",
"branch": "master",
"commit": "aa1497ed0949fd50e99e70d6324a29c5b34f9390",
"repoRoot": "/Users/zhongweili/projects/openmind/42plugin-data"
},
"manifest": {
"name": "dev-docs",
"description": "Command set for developer docs lookup and updates",
"version": "0.1.0"
},
"content": {
"files": [
{
"path": "README.md",
"sha256": "40558a0767033c64bc72443f4839d1d396bcb8822226017d77f287a003837cfd"
},
{
"path": ".claude-plugin/plugin.json",
"sha256": "016ac4095dd9d218ad953377476b2c4648b521b6f7ab2e5f6259ffac649a9b4c"
},
{
"path": "commands/dev-docs.md",
"sha256": "b57d5ebed8414e3d513200ab6cdd1ecfa8980a923ff2bf7563a265041df39b86"
}
],
"dirSha256": "d576cb4e57504e3555892fead8ab3c20efbf012caf5ce8955345b693c7320147"
},
"security": {
"scannedAt": null,
"scannerVersion": null,
"flags": []
}
}