Go

Skill anombyte93/prd-taskmaster/skills/go

Zero-config goal-to-tasks engine. Takes any goal (software, pentest, business, learning), runs adaptive discovery, generates a validated spec, parses into TaskMaster tasks, creates an implementation plan, and executes with built-in CDD verification. Use when user says "PRD", "product requirements", "I want to build", or any goal-driven phrase.From its SKILL.md

Install

npx -y skills add anombyte93/prd-taskmaster --skill go

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

runs commandsInstructs the agent to run 2 commands, including `ToolSearch(query="select:mcp__plugin_prd_go__preflight")` and 1 more.

SKILL.md

2.1 KB, 395 tokens by cl100k_base, as published. Nobody here has run it

go (orchestrator)

Pure routing. Reads pipeline state, dispatches to the correct phase skill.

Deferred MCP tools: in Claude Code the engine's MCP tools are often deferred — not callable until loaded. If a tool below is not directly callable, first run ToolSearch(query="select:mcp__plugin_prd_go__preflight") (keyword fallback ToolSearch(query="+atlas engine preflight", max_results=10)) and use whichever prefix matches (mcp__plugin_prd_go__ or mcp__atlas-engine__).

Flow

Call mcp__plugin_prd_go__preflight() — get environment state
Call mcp__plugin_prd_go__current_phase() — get pipeline state
Route via Skill tool:
- current_phase is null or SETUP → invoke /prd:setup
- current_phase is DISCOVER → invoke /prd:discover
- current_phase is GENERATE → invoke /prd:generate
- current_phase is HANDOFF → invoke /prd:handoff
- current_phase is EXECUTE → invoke /prd:execute-task
After phase skill returns, re-check current_phase. If it advanced, route to the next phase. If not, report the blocker.

Stateless routing

This skill does NOT hold procedure. Each phase skill owns its own logic. The orchestrator survives context loss because every phase skill reads current_phase() on entry.

Red flags

These thoughts mean STOP, you're rationalising:

"I know which phase we're in, skip preflight" → NO. Preflight is cheap.
"The phase skill already ran, I don't need to re-check" → NO. Context might have died.
"I can just do the work myself" → NO. Dispatch to the phase skill.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most product spec skills give in 395 tokens

Counted across 483 of the 502 authors here whose files we hold, read 2026-09-06

Write the PRD using the templatein 39 of 483, across 36 files
Ask one question at a timein 24 of 483
Write acceptance criteria in Given-When-Then formatin 24 of 483
Write user stories with acceptance criteriain 22 of 483, across 21 files
Respect ADRs in areas you touchin 21 of 483, across 17 files
Use the domain glossary vocabulary throughout the PRDin 20 of 483, across 16 files
Explore the repo to understand the current codebasein 19 of 483, across 15 files
Provide testable acceptance criteriain 19 of 483, across 17 files
Publish the PRD to the issue trackerin 18 of 483, across 14 files
Apply the ready-for-agent triage labelin 15 of 483, across 13 files
Prefer existing seams over new onesin 14 of 483, across 12 files
Save the PRD as a markdown filein 14 of 483, across 9 files

Said here and by no other author read

Call preflight to get environment state
Call current_phase to get pipeline state
Route to the phase skill matching current_phase
Re-check current_phase after the phase skill returns
Route to the next phase if it advanced
Report the blocker if the phase did not advance

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.