Speccrew product manager orchestration
Skill charlesmu99/speccrew/.speccrew/skills/speccrew-product-manager-orchestration
SpecCrew - An AI-driven software engineering framework that embeds a virtual AI development team into your projects. Supports specification-driven development (SDD) with PRD → Feature Design → System Design → Develop → System Test workflow.
npx -y skills add charlesmu99/speccrew --skill speccrew-product-manager-orchestrationAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Product Manager core orchestration skill (pure routing layer v2.0), responsible for workflow resume routing and dispatch-to-worker scheduling for each Phase Skill. All business logic is executed by independent Phase Skills.
SKILL.md
0.8 KB, 106 tokens by cl100k_base, as published. Nobody here has run it
Trigger Scenarios
- Product Manager Agent starts the PRD workflow for a new user requirement
- User submits a requirement and needs PRD generation
- Workflow resume after Phase checkpoint (resume_target routing)
AgentFlow Definition
<!-- @agentflow: SKILL.xml -->REQUIRED: Before executing this workflow, read the XML workflow specification: speccrew-workspace/docs/rules/agentflow-spec.md Then read and execute the XML workflow in SKILL.xml block-by-block as the authoritative execution plan.
Gives 0 of the 12 instructions most agent orchestration skills give in 106 tokens
Counted across 742 of the 995 authors here whose files we hold, read 2026-08-06
- run the full test suite after integrating changesin 53 of 742, across 20 files
- reference existing artifacts by path or URLin 52 of 742, across 22 files
- dispatch one agent per independent problem domainin 50 of 742, across 17 files
- verify fixes do not conflictin 45 of 742, across 13 files
- include a suggested skills section in the documentin 45 of 742, across 15 files
- redact sensitive informationin 41 of 742, across 11 files
- save to the temporary directory of the operating systemin 39 of 742, across 9 files
- tailor the document to user-provided focus argumentsin 39 of 742, across 9 files
- spot check agent changes for systematic errorsin 34 of 742, across 7 files
- write a handoff document summarising the current conversationin 31 of 742, across 6 files
- assign each agent a specific scopein 23 of 742, across 8 files
- provide specific scope and clear goalin 23 of 742, across 5 files
Said here and by no other author read
- read the agentflow specification before executing
- execute the XML workflow block-by-block
- route workflow resume targets
- dispatch scheduling to phase skills
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.