Claude Code Workflow that executes cys:plan implementation plans with independent tasks running in parallel via a dependency DAG — ships the cys plugin (design, plan, run, check, ship).
bacsystem/parallel-plan-executor
Skill Claude CodeCodex
Use when reviewing implemented work or before claiming anything is done, fixed or passing — adversarial review with explicit verdicts, and verification with evidence before assertions. The same conventions the parallel-plan-executor's review agents follow.
bacsystem/parallel-plan-executor
Skill Claude CodeCodex
Use BEFORE any creative or feature work — turning an idea into an approved design spec through collaborative dialogue. Triggers - "let's build X", "I want a feature that...", "help me design...". The cys flow starts here; the output spec feeds cys:plan.
bacsystem/parallel-plan-executor
Skill Claude CodeCodex
Use when starting work with the cys plugin or unsure which cys skill applies — the index of the cys flow (design → plan → run → check → ship) and the rules for moving between stages.
bacsystem/parallel-plan-executor
Skill Claude CodeCodex
Use when an approved design spec exists and you need the implementation plan — numbered tasks with Files and Consumes/Produces blocks that the parallel-plan-executor can parse into a dependency DAG. Comes after cys:design, before cys:run.
bacsystem/parallel-plan-executor
Skill Claude CodeCodex
Use when changes are ready to ship — takes the working tree to a pull request with code review, Conventional Commit, automatic SemVer bump and a PR template. Part of the cys flow (after cys:check).