ctx-plan-writing

Structured plan-writing skill adapted from obra/superpowers. Produces actionable plans that map directly to claude-ctx workflows and tasks.

⭐4stars🔀2forks📁View on GitHub🕐Updated Dec 31, 2025

When & Why to Use This Skill

The ctx-plan-writing skill is a specialized Claude agent tool designed to bridge the gap between brainstorming and execution. It transforms high-level ideas into structured, actionable project plans that map directly to automated workflows. By breaking down complex objectives into specific workstreams, defining 'Definition of Done' for every task, and incorporating risk mitigation strategies, this skill ensures that projects are executed with technical precision and organizational consistency.

Use Cases

  • Technical Roadmap Creation: Converting a messy brainstorming session into a structured execution plan with defined workstreams for frontend, backend, and infrastructure.
  • Task Standardization: Automatically generating detailed task lists with built-in validation hooks and testing requirements to ensure high-quality code delivery.
  • Risk Assessment and Mitigation: Identifying potential project bottlenecks and dependencies during the planning phase to establish rollback steps and safety guardrails.
  • Workflow Integration: Seeding execution tasks directly into a TUI or automated workflow system to streamline the transition from planning to active development.
namectx-plan-writing
descriptionStructured plan-writing skill adapted from obra/superpowers. Produces actionable plans that map directly to cortex workflows and tasks.
licenseMIT (obra/superpowers)
command/ctx:plan

/ctx:plan

Transforms brainstorm output into a concrete execution plan that cortex can enforce.

Inputs

  • Brainstorm summary (see /ctx:brainstorm).
  • Relevant workflows in workflows/ and rules in rules/Planning.md.
  • Any mandated modes (e.g., modes/Super_Saiyan.md, modes/Security_Audit.md).

Steps

  1. Restate Objective
    • One paragraph referencing ticket/issue + constraints.
  2. Identify Workstreams
    • Break work into 2–5 streams (frontend, backend, docs, infra, etc.).
    • For each, list required agents/modes/rules.
  3. Define Tasks per Stream
    • Bullet tasks with Definition of Done + validation (tests, lint, visual review).
    • Include verification hooks (rules/, commands/testing.yaml).
  4. Risk / Mitigation
    • Capture open questions, dependencies, rollback steps.
  5. Task Sync
    • For each bullet, create a Task TUI entry (press T → A).
    • OR run /ctx:execute-plan after this skill to auto-seed tasks (coming soon).

Output template

## Objective

## Workstreams
### Stream 1 – <name>
- Task … (agent/mode/rule, validation)
- Task …

### Stream 2 – …

## Risks & Mitigations
- …

Store the plan in chat + docs/plans/<date>-<slug>.md if long-lived. Then move to /ctx:execute-plan.

Resources

  • Plan template snippet: skills/collaboration/writing-plans/resources/template.md.