development-plan-doc-basic
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.
Source facts
- Repository
- Mr-Q526/TeamCC-Platform
- Last source activity
- April 15, 2026 at 03:16
- Detected SKILL.md language
- English
- Stars
- 7
- Forks
- 1
Install options
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Review the source files
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
File Explorer
4 filesShowing SKILL.md
SKILL.md
Source instructions · Read-only preview- 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
1. Restate the goal.
2. List likely files or modules to inspect.
3. Propose a few implementation steps.
4. Add a basic validation checklist.
5. Mention obvious risks.
## Output structure
1. Goal
2. Proposed steps
3. Files or modules
4. Validation
5. 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?
View on GitHub