skill-planning-format

Standardize markdown formats for development plans by enforcing specific file naming conventions like PLAN.md and TASK.md. This prevents planning rationalizations and ensures consistency across project tracking and execution by providing rigid structural templates.

Prevent developer rationalizations in project planning by mandating standardized PLAN.md and TASK.md markdown templates. Enforcing rigid required sections and strict file naming conventions actively discourages common excuses for poor planning and ensures detailed, actionable tasks.

Generate a standardized development plan by applying pre-built markdown templates to create your PLAN.md and TASK.md files. Specify required sections, utilize relative path linking for internal document references, and adhere to file naming conventions to ensure clarity.

Yes, this planning format requires strict file naming conventions for markdown documents, specifically mandating PLAN.md for development plans and TASK.md for detailed task descriptions. These rigid structures ensure consistency and easy tracking by the orchestrator.

Yes, you can use relative path linking for all internal document references in task management markdown. This standardized approach ensures that PLAN.md and TASK.md files maintain accurate internal connections without relying on absolute system paths.

You need rigid markdown templates for project task management when ensuring all new features are planned with detailed, actionable tasks. This standardization prevents poor planning, enforces required sections, and facilitates easy tracking and execution by the orchestrator.