cc-prd

Convert PRDs, feature specs, or design briefs into phased implementation plans.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/z23cc/cc-code --skill cc-prd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cc-prd
Source: https://github.com/z23cc/cc-code/tree/main/skills/cc-prd
Command: npx skills add https://github.com/z23cc/cc-code --skill cc-prd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a PRD, feature spec, or design brief into a concrete, phased implementation plan, aligning teams and milestones from brainstormed inputs.

Core Features & Use Cases

  • Phase-driven plan generation with explicit architectural decisions, vertical slices, and tracer bullets.
  • Supports import-ready outputs for cc-flow and cc-plan workflows.
  • Encourages explicit decisions, risk assessment, and open questions to reduce ambiguity.

Quick Start

Provide a PRD, spec, or design brief as input to generate a structured, phase-based implementation plan.

Frequently Asked Questions about cc-prd

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

FAQPage Schema
How do I convert a PRD into a phased implementation plan?

To convert a PRD into a phased implementation plan, provide your feature spec or design brief as input to generate a structured plan with explicit architectural decisions, vertical slices, and tracer bullets.

What is the best way to structure vertical slices from a feature spec?

The best way to structure vertical slices from a feature spec is to enforce explicit architectural decisions and phased timelines, reducing ambiguity by tracking risks and documenting open questions alongside tracer bullets.

How does tracer bullet planning work for design briefs?

Tracer bullet planning for design briefs works by generating a concrete, phase-driven implementation plan that aligns milestones and architectural decisions, translating brainstormed inputs into actionable, import-ready workflows.

Can I import phased plans directly into cc-flow workflows?

Yes, you can import phased plans into cc-flow and cc-plan workflows because the Skill generates import-ready outputs designed specifically for product and engineering workflows that translate brainstorm outputs into actionable plans.

Does implementation plan generation include risk tracking and open questions?

Implementation plan generation includes risk tracking and open questions to reduce ambiguity, enforcing explicit decisions alongside phased timelines, architectural choices, and vertical slices.

Why use a phased plan instead of a single roadmap for product development?

Use a phased plan instead of a single roadmap to break brainstormed inputs into concrete milestones with tracer bullets and vertical slices, ensuring explicit architectural decisions and risk assessment reduce ambiguity.