work-pipeline

1# WORK-PIPELINE Trigger
2 
3When the user's message starts with a `[]` tag, start the WORK-PIPELINE by reading `../skills/sdd-pipeline/references/agent-flow.md` and following the orchestration flow.
4 
5## Trigger Detection
6 
7Any message starting with `[...]` triggers this pipeline:
8- `[new-feature]`, `[enhancement]`, `[bugfix]`, `[new-work]`, `[WORK start]`
9- Or any custom tag in square brackets
10 
11## References Directory (CRITICAL)
12 
13When this skill is triggered, Claude Code provides the "Base directory for this skill" as an absolute path.
14Derive the **REFERENCES_DIR** from it:
15 
16```
17REFERENCES_DIR = {Base directory}/../sdd-pipeline/references
18```
19 
20You MUST pass this absolute path to **every sub-agent invocation** (specifier, planner, scheduler, builder, verifier, committer).
21Include it at the top of the prompt text:
22 
23```
24REFERENCES_DIR={absolute_path}
25```
26 
27Sub-agents need this path to read their reference files. Without it, they cannot find the files and will loop.
28 
29## Pipeline Flow
30 
311. **Call specifier agent** — analyzes the requirement, creates `works/WORK-NN/Requirement.md`, determines execution-mode (direct/pipeline/full)
322. **⛔ STOP — Present the specifier's output summary to the user and WAIT for explicit approval.** Do NOT call the next agent until the user approves. Show what was created (Requirement.md, PLAN.md if direct mode, TASK files) and ask "Proceed?"
333. **Follow the execution-mode** returned by specifier:
34   - `direct`: call builder → committer
35…