High-level orchestration skill for QEC research workflows. Initializes and updates project state, keeps a durable research log, routes work to future domain skills and MCP backends, and enforces explicit validation and provenance.
Use this skill to coordinate a QEC research task at the project level:
Use this skill when the user asks for overall project progress, research planning, repo structure, state updates, or cross-cutting workflow decisions.
Do not use this skill when a narrower domain skill exists and the task is purely local to that workflow.
Required files:
research-state.yamlresearch-log.mdAssumptions:
research-state.yaml.research-log.md.research-state.yaml and research-log.md before closing substantive work.Before closing work:
Problem: the repo structure evolves, but the state file still describes an older plan.
Fix: update current_focus, phase, decisions, and next_actions together.
Problem: too many skills get proposed before the core contract exists.
Fix: record the proposed skill in the backlog, but do not add it until it supports a real demo or workflow.
Problem: a plan assumes Stim, ldpc, Lean, or QUITS without stating why.
Fix: add the backend decision and rationale to research-state.yaml.