mcpbeat

Go

anombyte93/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.

541 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
585
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/anombyte93/prd-taskmaster --skill go

The instruction itself

4 sections, as written by the author

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.

How to use it

Copy the folder

Take anombyte93/go from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.