Skill

writing-plans

Generates structured execution plans from brainstorm summaries, breaking into workstreams with tasks, definitions of done, validations, risks, and mitigations for cortex workflows.

developer-tools

npx claudepluginhub nickcrew/claude-cortex

Tool Access

This skill uses the workspace's default tool permissions.

Preview

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

Supporting Assets

resources/template.md

SKILL.md

Similar Skills

ce:plan

13.2k

Creates structured plans for multi-step tasks including software features, implementations, research, or projects. Deepens plans via interactive sub-agent reviews.

4 files

compound-engineering

spec-plan

Creates structured plans for multi-step tasks like software features, research workflows, events, or study plans. Deepens existing plans with interactive sub-agent reviews.

4 files

spec-first

plan-crafting

Generates executable Markdown implementation plans for multi-step tasks from context briefs, resolving ambiguities, ordering dependencies, and enabling parallel worker execution.

engineering-discipline

Stats

Stars15

Forks6

Last CommitApr 23, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

/collaboration:writing-plans

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

Restate Objective

One paragraph referencing ticket/issue + constraints.

Identify Workstreams

Break work into 2–5 streams (frontend, backend, docs, infra, etc.).
For each, list required agents/modes/rules.

Define Tasks per Stream

Bullet tasks with Definition of Done + validation (tests, lint, visual review).
Include verification hooks (rules/, commands/testing.yaml).

Risk / Mitigation

Capture open questions, dependencies, rollback steps.

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.

`/collaboration:writing-plans`

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

Restate Objective
- One paragraph referencing ticket/issue + constraints.
Identify Workstreams
- Break work into 2–5 streams (frontend, backend, docs, infra, etc.).
- For each, list required agents/modes/rules.
Define Tasks per Stream
- Bullet tasks with Definition of Done + validation (tests, lint, visual review).
- Include verification hooks (rules/, commands/testing.yaml).
Risk / Mitigation
- Capture open questions, dependencies, rollback steps.
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.