$ywc
8 stars
Guidebook / Core pipeline

05. Handling work split into multiple Tasks (general cycle - medium/large)

Guide3 min read

If any of the following applies, ywc-plan routes to this path.

Choose by scale

04. Handling a small change (general cycle - small)When ywc-plan judges a request as Small , it automatically enters this path.You are here05. Handling work split into multiple Tasks (general cycle - medium/large)If any of the following applies, ywc-plan routes to this path.06. Finish automatically from one goal (ywc-agentic)04 and 05 are manual control flows where the user invokes each step one by one ( ywc-plan -> ...

Back to table of contents

05. Handling work split into multiple Tasks (general cycle - medium/large)

When to use this flow

If any of the following applies, ywc-plan routes to this path.

  • The change is hard to fit into a single reviewable PR (multiple screens, multiple APIs, multiple subsystems)
  • It includes a DB migration (always this path regardless of scale - Safety Invariant)
  • It introduces a new Library/Framework (also always this path)

Overall flow

guidebook
ywc-plan -> ywc-spec-ready -> ywc-task-generator -> ywc-sequential-executor --review or ywc-parallel-executor --review
StepSkillRole
1ywc-planAnalyze the request and create a docs/ywc-plans/<slug>.md spec
2ywc-spec-readyAutomatically repeat ywc-plan --update-spec and ywc-spec-validate until the spec is DONE
3ywc-task-generatorDecompose the DONE spec into dependency-safe Tasks (tasks/<phase>-<sequence>-<slug>/)
4ywc-sequential-executor or ywc-parallel-executorActually implement Tasks -> PR -> Merge

How to choose Sequential vs Parallel

SituationChoice
Task order matters, or Tasks depend on one another's outputsywc-sequential-executor
Tasks are independent and grouped into parallelizable waves in dependency-graph.mdywc-parallel-executor (isolated with Git Worktrees)

Example run

claude code
ywc-plan Users need a settings screen and API to turn notification types on/off individually. Support email/push/in-app, 3 channels
claude code
ywc-spec-ready --spec docs/ywc-plans/notification-settings.md
claude code
ywc-task-generator --lang ko

The execution commands after this have many options, so they are covered on a separate page: 16. Executor / Code-gen Prompt patterns. The simplest starting point is:

claude code
ywc-sequential-executor --review

If you omit the task, it automatically finds the next executable Task from dependency-graph.md.

Always include --review

Both executors use the --review flag to automatically run /ywc-impl-review before PR creation/merge for each Task. Running without this flag is equivalent to completely skipping the review step in the small cycle from 04. There is no good reason to omit it. (If a Task has Criticality: critical, review is forced regardless of the flag.)

When you get blocked at each step

SituationAction
ywc-spec-ready reaches the iteration limitA fundamental spec issue is preventing automatic convergence - read the partial report and edit the spec directly
ywc-task-generator tries to create 20 or more TasksThis signals that the spec itself is too large - consider splitting the spec first
A dependency is not completed during Task executionThe executor stops automatically and reports which Task must precede the current one

Previous: 04. Handling a small change - Next: 06. Finish automatically from one goal