Writing Plans FAQs

Question 1

When should I use the Writing Plans skill?

Accepted Answer

You should activate this skill after you have a project specification or design but before you begin coding. It is specifically designed for multi-step tasks where organization, dependency tracking, and architectural documentation are required.

Question 2

What are Epics and Tasks in the context of this skill?

Accepted Answer

Epics are parent structures that document high-level design decisions, architecture rationale, and patterns. Tasks are child structures that contain specific implementation details, including file paths, exact code snippets, and shell commands for execution.

Question 3

What does the Writing Plans skill do?

Accepted Answer

The Writing Plans skill generates granular, hierarchical implementation roadmaps for technical projects. It breaks down complex requirements into Epics (for design rationale) and Tasks (for atomic execution steps), ensuring every part of a project is documented before a single line of code is written.

Question 4

How does Writing Plans handle project dependencies?

Accepted Answer

The skill utilizes a 'beads' system to model relationships. It allows you to link tasks to epics and create blocks between tasks to ensure work is performed in the correct execution order, preventing premature implementation of dependent features.

Question 5

How does this skill improve my development workflow?

Accepted Answer

It reduces cognitive load by enforcing 'bite-sized' granularity—breaking work into 2-5 minute execution steps. It also mandates best practices like Test-Driven Development (TDD), DRY principles, and frequent commits, resulting in higher code quality and fewer regressions.

Writing Plans

Writing Plans

About

Key Features

Use Cases

About

Key Features

Use Cases