go

ゼロコンフィケーションの目標タスクエンジン。ソフトウェア、ペンテスト、ビジネス、学習などの目標を扱い、適応型ディスカバリーを実行し、検証済み仕様を生成し、TaskMasterタスクに解析し、実装計画を作成し、組み込みのCDD検証で実行します。

@anombyte93MIT更新 2026-08-22v0.1.0直近30日 0 回
コンテキストを 394 トークン使用しますコンテキストを 394 トークン 使用します

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

  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.