writing-plans

Convert a written spec into a step-by-step implementation plan.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/Kraits/cxc-ace --skill writing-plans-kraits
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/Kraits/cxc-ace/tree/main/skills-backup/writing-plans
Command: npx skills add https://github.com/Kraits/cxc-ace --skill writing-plans-kraits

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write comprehensive implementation plans from a spec so engineers can start coding with a clear roadmap.

Core Features & Use Cases

  • Structured planning: generate an end-to-end plan mapping tasks, files, tests, docs, and commits.
  • Deterministic steps: break work into bite-sized tasks suitable for a work breakdown.
  • Contextual guidance: tailor plans to unfamiliar codebases and tech stacks.

Quick Start

To create a plan for a new feature, feed the spec into the planning tool and request a full implementation plan.

Frequently Asked Questions about writing-plans

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a spec into a step-by-step implementation plan?

To turn a spec into an implementation plan, feed the written spec into the planning tool to generate a structured roadmap mapping tasks, files, tests, docs, and commits.

What is the best way to break down engineering tasks for unfamiliar codebases?

The best way to break down tasks for unfamiliar codebases is to enforce a structured plan template that delivers bite-sized, deterministic steps with clear deliverables before coding begins.

Can I generate a test plan and documentation roadmap from a feature spec?

Yes, you can generate a test plan and documentation roadmap from a feature spec by mapping the end-to-end work scope across code, tests, docs, and release commits.

Does this planning tool work for multi-step tasks involving code and release commits?

Yes, this planning tool works for multi-step tasks involving code and release commits by tailoring contextual guidance to the specific tech stack and enforcing deterministic task granularity.

Why do I need an implementation plan before coding a new feature?

You need an implementation plan before coding to ensure engineers have a clear roadmap with structured deliverables, preventing scope creep and aligning tests with release commits.

What should an implementation plan include for a work breakdown structure?

An implementation plan for a work breakdown structure should include end-to-end task mapping, file modifications, test plans, documentation updates, and specific release commit deliverables.