Skip to content

davepoon/buildwithclaude / plugins/agents-uc-taskmanager/skills/work-pipeline

work-pipeline

Verified

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.

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/references

You 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

  1. Call specifier agent — analyzes the requirement, creates works/WORK-NN/Requirement.md, determines execution-mode (direct/pipeline/full)
  2. ⛔ 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?"
  3. Follow the execution-mode returned by specifier:
    • direct: call builder → committer
    • pipeline: call builder → verifier → committer in sequence
    • full: 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

writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 321kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall