Generate OpenSpec design.md and tasks.md artifacts before coding.
npx skills add https://github.com/tody-agent/codymaster --skill cm-planning
Please help me install this Agent Skill. Skill: cm-planning Source: https://github.com/tody-agent/codymaster/tree/main/skills/cm-planning Command: npx skills add https://github.com/tody-agent/codymaster --skill cm-planning
Planning before execution to align intent, requirements, and design across multi-step tasks.
Run cm-planning to produce an OpenSpec-style design and an implementation task list before coding.
High-intent search queries and answers about installing and using this skill.
Planning before coding aligns intent, requirements, and design by brainstorming goals, defining scope, and generating OpenSpec artifacts like design.md and tasks.md to document the plan.
Scoping multi-step projects involves brainstorming to understand constraints and identify options, then producing an OpenSpec-style design document and a phase-based implementation task list before execution.
You do not need an existing OpenSpec setup to document plans, as the planning workflow generates OpenSpec-style artifacts like design.md and tasks.md directly, providing a repeatable framework for your projects.
Yes, you can use brainstorming to define scope and identify options for initiative planning, helping you understand goals and constraints before generating the required design and task documentation.
Pre-execution planning is not suited for simple, single-step tasks that require no documented design, as the workflow targets multi-step projects, feature definitions, and initiatives needing phase-based artifacts.
AzrinPutraGuide exploratory conversations to elicit project requirements and generate an intent brief.
JaimeJunrExecutes implementation plans from tasks.md with phase-based task coordination.
marcuskroghGenerate structured BUG.md files with repro steps and acceptance criteria.
MaxServDevCreate, list, update, and delete manual to-do tasks via local_tasks.
