Work Pipeline
Triggers the WORK-PIPELINE when a user request starts with a [] tag (e.g., [new-feature], [bugfix], [WORK start]). Use this skill whenever you detect a [] tag at the beginning of a user message.
Install
$ agentstack add skill-davepoon-buildwithclaude-work-pipeline ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-davepoon-buildwithclaude-work-pipeline) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
WORK-PIPELINE Trigger
When 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.
Trigger Detection
Any message starting with [...] triggers this pipeline:
[new-feature],[enhancement],[bugfix],[new-work],[WORK start]- Or any custom tag in square brackets
References Directory (CRITICAL)
When this skill is triggered, Claude Code provides the "Base directory for this skill" as an absolute path. Derive the REFERENCES_DIR from it:
REFERENCES_DIR = {Base directory}/../sdd-pipeline/referencesYou MUST pass this absolute path to every sub-agent invocation (specifier, planner, scheduler, builder, verifier, committer). Include it at the top of the prompt text:
REFERENCES_DIR={absolute_path}Sub-agents need this path to read their reference files. Without it, they cannot find the files and will loop.
Pipeline Flow
- Call specifier agent — analyzes the requirement, creates
works/WORK-NN/Requirement.md, determines execution-mode (direct/pipeline/full) - ⛔ 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?"
- Follow the execution-mode returned by specifier:
direct: call builder → committerpipeline: call builder → verifier → committer in sequencefull: call planner → ⛔ STOP for 2nd approval → scheduler → [builder → verifier → committer] × N
Auto Mode
If the user's message ends with "auto" or "자동으로", skip ALL approval steps and execute the entire pipeline automatically. This is the ONLY case where approval gates can be skipped.
Arguments
User requirement: $ARGUMENTS
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: davepoon
- Source: davepoon/buildwithclaude
- License: MIT
- Homepage: https://www.buildwithclaude.com
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.