| schemaVersion | "2026-04-11T00:00:00.000Z" |
| skillId | general/development-plan-doc-basic |
| name | development-plan-doc-basic |
| displayName | Development Plan Document Basic |
| description | Use as a lightweight baseline/control skill for creating a simple development plan or implementation outline. Basic version focuses on high-level steps, rough files, and validation notes with limited repository research and limited method/type-level detail. |
| aliases | ["development-plan-doc-basic","Development Plan Document Basic","development plan doc basic","developmentplandocbasic","开发计划文档","功能开发规划","技术方案","实施方案","简单计划","任务拆解","basic plan","control skill","baseline skill","coding plan","implementation plan","plan","计划","开发计划"] |
| version | 0.1.0 |
| sourceHash | sha256:45b976a534e792ac631a62b46d8d635d782cb571197a2cab2a7cd5ee6f9d1af0 |
| domain | general |
| departmentTags | ["backend-platform","frontend-platform"] |
| sceneTags | ["architecture","planning"] |
Development Plan Document Basic
Use this skill as a simple baseline for development planning.
Goal: produce a short, understandable implementation outline quickly.
Basic workflow
- Restate the goal.
- List likely files or modules to inspect.
- Propose a few implementation steps.
- Add a basic validation checklist.
- Mention obvious risks.
Output structure
- Goal
- Proposed steps
- Files or modules
- Validation
- Risks
Rules
- Keep the plan concise.
- Avoid deep type or method definitions unless requested.
- Do not over-invest in repository archaeology.
- Prefer practical next steps over exhaustive architecture.
Final checks
- Is there a clear order of work?
- Are validation steps present?
- Are obvious risks mentioned?
