agentleFS
Sign inStart free
anombyte93anombyte93/prd-taskmaster/skills/go/SKILL.md

go

Skill608 starsChanged 9 months agoMITView on GitHub

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.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Call mcp__plugin_prd_go__preflight() — get environment state

    line 46
  2. Very specific:

    Call mcp__plugin_prd_go__current_phase() — get pipeline state

    line 47
  3. Distinctive:

    After phase skill returns, re-check current_phase.

    line 55

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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__).

Provider-aware routing before file-mode pipeline state

Resolve SKILL.md Phase 0, then doctor --project-root ROOT (MCP doctor) before the legacy Flow below. Read its config even if the result is not ok: on a fresh project, missing board/reference gives UNKNOWN reachability, not file-mode selection. For atlas-kanban, route /prd:setup, /prd:discover, /prd:generate, then /prd:handoff through their provider-aware entry branches. Preserve the approved spec, plan and canonical reference outputs between phases. Do not enter the file-task pipeline's current_phase/advance_phase loop or route /prd:execute-task: canonical execution belongs to the parent's reservation/external-session protocol. Report actual artifacts/canonical IDs, never manufacture file-mode gate evidence. The Flow below applies only to taskmaster-file, including existing legacy stores.

Flow

  1. Call mcp__plugin_prd_go__preflight() — get environment state
  2. Call mcp__plugin_prd_go__current_phase() — get pipeline state
  3. 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
  4. 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free