go

Name: go
Author: anombyte93

582stars57forks

How to install go?

anombyte93/prd-taskmaster/go

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

Installs into the current project.

Summary

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", "pro

Files · 1

View on GitHub

SKILL.md

1	# go (orchestrator)
2
3	Pure routing. Reads pipeline state, dispatches to the correct phase skill.
4
5	Deferred MCP tools: in Claude Code the engine's MCP tools are often deferred — not
6	callable until loaded. If a tool below is not directly callable, first run
7	`ToolSearch(query="select:mcp__plugin_prd_go__preflight")` (keyword fallback
8	`ToolSearch(query="+atlas engine preflight", max_results=10)`) and use whichever prefix
9	matches (`mcp__plugin_prd_go__` or `mcp__atlas-engine__`).
10
11	## Flow
12
13	1. Call `mcp__plugin_prd_go__preflight()` — get environment state
14	2. Call `mcp__plugin_prd_go__current_phase()` — get pipeline state
15	3. Route via Skill tool:
16	- current_phase is null or SETUP → invoke `/prd:setup`
17	- current_phase is DISCOVER → invoke `/prd:discover`
18	- current_phase is GENERATE → invoke `/prd:generate`
19	- current_phase is HANDOFF → invoke `/prd:handoff`
20	- current_phase is EXECUTE → invoke `/prd:execute-task`
21
22	4. After phase skill returns, re-check current_phase. If it advanced, route to the next phase. If not, report the blocker.
23
24	## Stateless routing
25
26	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.
27
28	## Red flags
29
30	These thoughts mean STOP, you're rationalising:
31	- "I know which phase we're in, skip preflight" → NO. Preflight is cheap.
32	- "The phase skill already ran, I don't need to re-check" → NO. Context might have died.
33	- "I can just do the work myself" → NO. Dispatch to the phase skill.

People who liked this also viewed

6 picks

Type

go

582stars57forks

View on GitHub

How to install go?

anombyte93/prd-taskmaster/go

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

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# go (orchestrator)
2
3	Pure routing. Reads pipeline state, dispatches to the correct phase skill.
4
5	Deferred MCP tools: in Claude Code the engine's MCP tools are often deferred — not
6	callable until loaded. If a tool below is not directly callable, first run
7	`ToolSearch(query="select:mcp__plugin_prd_go__preflight")` (keyword fallback
8	`ToolSearch(query="+atlas engine preflight", max_results=10)`) and use whichever prefix
9	matches (`mcp__plugin_prd_go__` or `mcp__atlas-engine__`).
10
11	## Flow
12
13	1. Call `mcp__plugin_prd_go__preflight()` — get environment state
14	2. Call `mcp__plugin_prd_go__current_phase()` — get pipeline state
15	3. Route via Skill tool:
16	- current_phase is null or SETUP → invoke `/prd:setup`
17	- current_phase is DISCOVER → invoke `/prd:discover`
18	- current_phase is GENERATE → invoke `/prd:generate`
19	- current_phase is HANDOFF → invoke `/prd:handoff`
20	- current_phase is EXECUTE → invoke `/prd:execute-task`
21
22	4. After phase skill returns, re-check current_phase. If it advanced, route to the next phase. If not, report the blocker.
23
24	## Stateless routing
25
26	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.
27
28	## Red flags
29
30	These thoughts mean STOP, you're rationalising:
31	- "I know which phase we're in, skip preflight" → NO. Preflight is cheap.
32	- "The phase skill already ran, I don't need to re-check" → NO. Context might have died.
33	- "I can just do the work myself" → NO. Dispatch to the phase skill.

People who liked this also viewed

6 picks

Type