plugins/agents-uc-taskmanager/skills/work-pipeline/SKILL.md
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.
npx skillsauth add davepoon/buildwithclaude work-pipelineInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
Any message starting with [...] triggers this pipeline:
[new-feature], [enhancement], [bugfix], [new-work], [WORK start]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.
works/WORK-NN/Requirement.md, determines execution-mode (direct/pipeline/full)direct: call builder → committerpipeline: call builder → verifier → committer in sequencefull: call planner → ⛔ STOP for 2nd approval → scheduler → [builder → verifier → committer] × NIf 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.
User requirement: $ARGUMENTS
tools
Assesses the current state of the startup project and recommends what to focus on next. Use when there is a need or a question from the user to understand what the next steps are or what to focus on next.
data-ai
Use at the start of any conversation about a startup idea, product validation, founder strategy, or work inside a `startup/` workspace. Establishes file conventions, voice-input handling, subagent dispatch rules, and how to update each artifact safely. Activate before invoking any other startup-superpowers skill.
tools
Manages the founder's survey-based validation — crafting the right questions, deploying a survey to the internet, and analyzing results against hypotheses. Use when the founder wants to run a survey, create survey questions, validate hypotheses at scale, check how a survey is going, understand whether a survey is the right tool right now, or deploy a question set to get quantitative signal. Also bring this up if you believe that creating a survey to collect quantitative evidence may be useful at this point.
development
Guides the founder through designing and optionally building the simplest MVP or prototype that validates their current hypotheses. Use when the founder wants to build something to test assumptions, discusses what to build next, wants to interpret results from a live MVP, or is deciding whether the current approach is still right. Also use when a founder proposes something to build — the skill will check whether the proposed form is the simplest thing that generates honest signal.