Translate product or project specs into step-by-step implementation plans.
npx skills add https://github.com/xaionaro/.config-codex --skill writing-plans-xaionaro
Please help me install this Agent Skill. Skill: writing-plans Source: https://github.com/xaionaro/.config-codex/tree/main/skills/writing-plans Command: npx skills add https://github.com/xaionaro/.config-codex --skill writing-plans-xaionaro
Translate a product or project spec into actionable, step-by-step implementation plans before coding. It ensures engineers have a clear, end-to-end plan that covers files, tests, docs, and commits.
Provide a complete, executable implementation plan for the feature and save it to docs/plans with clear tasks and checkpoints.
High-intent search queries and answers about installing and using this skill.
To create an implementation plan from a software spec, you translate the project requirements into actionable, step-by-step tasks. This ensures engineers have a clear, end-to-end plan covering concrete files, tests, and documentation before coding begins.
The best way to break down a project spec is through structured task decomposition. This process maps bite-sized, verifiable implementation steps directly to concrete files and tests, ensuring the entire feature scope is manageable.
Structure software development plans using a standardized format that lists touched files, tests, docs, and commits. Consistently save these plans to the docs/plans directory using a YYYY-MM-DD-feature-name.md naming convention.
Yes, this planning approach supports cross-functional task decomposition for features or subsystems. It breaks down complex specs into bite-sized, verifiable steps suitable for diverse software development planning needs.
A software implementation plan should include specific touched files, required tests, necessary documentation, and commit checkpoints. Mapping tasks to these concrete components prevents scope creep and ensures verifiable progress.
You need to generate a step-by-step implementation plan before coding whenever you start a new feature or subsystem. It applies to software development planning, architecture brainstorming, and translating project specs into actionable tasks.
Tristan578Draft SpawnForge feature specs with acceptance criteria and success metrics.
TalonT-OrgApply targeted code fixes to failing test suites in a Git worktree.
14790897Create and evaluate Architecture Decision Records documenting technical trade-offs.
januarfontiGenerate task lists with sub-tasks and relevant files from specifications.
