Every capability, one catalog.
One portable catalog projected into three runtimes. Entry routers own whole pipelines; stages are the sealed workers they dispatch.
Research first
Shared upfront research that surveys academic, technology, or market sources before downstream routing.
Creates persistent analysis of existing code, papers, or documents; initial analysis defaults here unless read-only/no-file or another primary applies.
Code & experiments
Create or update requirements/blueprints while keeping `prd.md` as the only spec-change path.
Code-work entrypoint that detects spec context and closes the plan→execute→test→report loop.
Rapid experiment prototyping around training setup and checkpoint evaluation/analysis.
Prepare application deployment/release setup and a ship checklist.
Analyze code, write a detailed implementation plan, and run the plan-check gate at the rigor derived from intensity.
Execute a plan step by step, delegate implementation to the development role, and record an execution log.
Revise an existing plan using user notes, plan-check feedback, and verification-failure notes.
Verify implementation results in stages and record evidence.
Assemble code-cycle results into a user-facing report.
Documents
Document-drafting pipeline that produces an applicable artifact through strategy, drafting, verification, and editing.
Correct and update existing document/research artifacts while preserving snapshots and change history.
Apply a cheatsheet draft to the real source artifact and verify the result.
Create an initial document strategy and evidence-based writing plan.
Refine a draft by applying memo/review feedback to a document strategy or draft.
Design
Visual-design pipeline coordinating references→tokens→components→review→handoff.
Bootstrap the design environment and state.
Collect external and user-provided visual references and create a brief.
Define design tokens such as color, typography, and spacing.
Build UI components/mockups and preview artifacts.
Review design output for quality, token-contract compliance, and breakage.
Package design results as assets and specifications for development handoff.
Cross-project & operations
Create or update a cross-project user-preference profile from coding, writing, and analysis patterns.
Read-oriented post-run inspection for artifact drift, inconsistency, and omissions.
Store project/cross-project notes and handoffs in working memory.