Skip to content

docs: fix inaccurate descriptions in Basic Workflow README section (#1) #1578

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Valentin-Laurent wants to merge 2 commits into
base: main
Choose a base branch
from
+10 −9
Open

docs: fix inaccurate descriptions in Basic Workflow README section (#1) #1578

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
23f40c1
docs: fix inaccurate descriptions in Basic Workflow README section (#1)
Copilot May 18, 2026
bef8b97
README: align Basic Workflow step naming and nested list structure (#2)
Copilot May 18, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 10 additions & 9 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -153,19 +153,20 @@ already use it in another harness.

## The Basic Workflow

1. **brainstorming** - Activates before writing code. Refines rough ideas through questions, explores alternatives, presents design in sections for validation. Saves design document.
1. **brainstorming** - Activates before any implementation work. Refines rough ideas through questions, explores alternatives, presents design in sections for validation. Saves design document.

2. **using-git-worktrees** - Activates after design approval. Creates isolated workspace on new branch, runs project setup, verifies clean test baseline.
2. **writing-plans** - Invoked by brainstorming after spec approval. Breaks work into bite-sized tasks (2-5 minutes each). Every task has exact file paths, complete code, verification steps.

3. **writing-plans** - Activates with approved design. Breaks work into bite-sized tasks (2-5 minutes each). Every task has exact file paths, complete code, verification steps.
3. **using-git-worktrees** - Activates before executing the plan. Creates isolated workspace on new branch, runs project setup, verifies clean test baseline.

4. **subagent-driven-development** or **executing-plans** - Activates with plan. Dispatches fresh subagent per task with two-stage review (spec compliance, then code quality), or executes in batches with human checkpoints.
4. **subagent-driven-development** / **executing-plans** - Repeat per task:
1. Choose your execution path:
- **subagent-driven-development** *(preferred — requires subagent support)* — Dispatches a fresh subagent per task with two-stage review (spec compliance, then code quality).
- **executing-plans** *(fallback)* — Executes tasks in a separate session, stopping only on blockers.
2. **test-driven-development** — Enforces RED-GREEN-REFACTOR: write failing test, watch it fail, write minimal code, watch it pass, commit.
3. **requesting-code-review** — Reviews against plan, reports issues by severity. Critical issues block progress.

5. **test-driven-development** - Activates during implementation. Enforces RED-GREEN-REFACTOR: write failing test, watch it fail, write minimal code, watch it pass, commit. Deletes code written before tests.

6. **requesting-code-review** - Activates between tasks. Reviews against plan, reports issues by severity. Critical issues block progress.

7. **finishing-a-development-branch** - Activates when tasks complete. Verifies tests, presents options (merge/PR/keep/discard), cleans up worktree.
5. **finishing-a-development-branch** - Activates when tasks complete. Verifies tests, presents options (merge/PR/keep/discard), cleans up worktree if it was created by Superpowers.

**The agent checks for relevant skills before any task.** Mandatory workflows, not suggestions.

Expand Down