dev-planning

Development planning and preparation

Dependency specification

#[[file:../rules/review-base.md]] #[[file:../rules/git-workflow.md]] #[[file:../rules/coding-standards.md]] #[[file:../rules/ui-design.md]] #[[file:../rules/project-structure.md]] #[[file:../task-breakdown/SKILL.md]]

Purpose

Align on the technical solution, complete task breakdown and common module design, and reduce uncertainty in the development phase.

Input

• Design document: module division plan and design decision records, or conversation context

Steps

For each step, output the title first, then the result

• Technical alignment:
  • Gather preferences: ask the developer about technical preferences (language, framework, existing constraints, etc.)
  • Provide recommendations: combine requirements, design, and developer input to give best-practice recommendations with rationale
  • Confirm the solution: the developer confirms or adjusts it, and the technical solution is finalized
• UI design (web projects only): after the technical solution is confirmed, if it is a web project, ask the developer whether design mockups are needed; if needed, comply with ui-design the specifications in
• Task breakdown: follow the steps in the task-breakdown skill, and output the task list and dependency table
• Project initialization:
  • Initialize the project according to the technical solution, including basic configuration and dependency installation
  • Check whether .gitignorealready exists; if not, generate it according to the tech stack
  • Create .env.example, distinguish dev/staging/prod, explain the purpose of each variable, and do not commit sensitive values to the repository
• Common modules: identify common modules, output interface specifications, and after confirmation prioritize development in this phase; usage documentation must be included, and web projects must include a unified demo entry page
• Specification conventions: agree on coding-standards, which will be enforced in subsequent development
• Write to documentation: write to documentation according to the output requirements (paths comply with the project-structure documentation storage specification)
• Perform review: comply with review-base, and only proceed to the next step after passing
• Commit: after review passes, commit according to git-workflow (including all artifacts from requirements analysis, software design, and development planning)

Output

• Technical solution: the confirmed technical solution
• Task list: a functional task list, broken down into tasks that can be independently developed and reviewed
• Common modules: list + interface specifications + usage documentation (web projects include a demo entry page)

Review checklist

• Technical solution: confirmed
• Task breakdown: each task can be independently developed and reviewed
• Common modules: complete list, interface specifications output, usage documentation available (web projects have a demo entry page)
• Specification conventions:coding-standards confirmed
• Environment variables: dev/staging/prod distinguished, not hardcoded

Phase end

Next phase:coding

#[[file:../rules/stage-gate.md]]