write-plan

Convert a brainstorm design summary into an immutable epic with a first task.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/sQVe/cape --skill write-plan-sqve
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-plan
Source: https://github.com/sQVe/cape/tree/main/skills/write-plan
Command: npx skills add https://github.com/sQVe/cape --skill write-plan-sqve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Formalizes a brainstorm design into an immutable epic with a first task, preserving context and preventing drift between ideation and implementation.

Core Features & Use Cases

  • Validates the existence of a design summary and enforces a contract for implementation.
  • Generates an epic with immutable requirements, anti-patterns, and success criteria using a standard template.
  • Creates a single, end-to-end vertical slice as the initial task to guide iterative development.
  • Provides a clear transition workflow from brainstorm to execution and validation.

Quick Start

Run cape:brainstorm to generate a design summary, then run cape:write-plan to formalize it into an epic and the first task.

Frequently Asked Questions about write-plan

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

FAQPage Schema
How do I turn a brainstorm design summary into an actionable epic?▼

To turn a brainstorm design summary into an actionable epic, use a formalization workflow that validates the design summary, enforces a fixed epic structure with immutable requirements, and generates an initial verifiable task.

How do I prevent scope drift between project ideation and implementation?▼

Prevent scope drift between project ideation and implementation by formalizing the design summary into an immutable epic. This contract enforces fixed requirements, anti-patterns, and success criteria to preserve context during execution.

What is the best way to create the first task for a new project epic?▼

The best way to create the first task for a new project epic is to generate a single, end-to-end vertical slice. This initial task provides clear success criteria to guide iterative development directly from the design summary.

Do I need a design summary before formalizing a project epic?▼

Yes, you need a design summary before formalizing a project epic. The workflow validates the existence of a brainstorm design summary to ensure there is a verified contract for implementation before generating the epic and initial task.

What structure is required for an epic to ensure verifiable implementation?▼

An epic structure that ensures verifiable implementation requires immutable requirements, defined anti-patterns, and clear success criteria. This fixed template creates a standardized contract for tracking execution and validation.