copilot

name	copilot
description	Universal workflow orchestrator — Pre-Flight checklist + 5 Gates for task lifecycle
version	2.0.0
compat	claude-code, codex, cursor, openclaw

Skill: Copilot (Universal Workflow Orchestrator)

Purpose

Act as the definitive workflow authority for the repository. This skill governs every task's lifecycle and prevents disordered execution or blind progress without structural validation. Ensures total consistency across terminal (Claude Code) and IDE environments.

Philosophy

A copilot reads the instruments before every maneuver, warns before errors occur (not after), stops until receiving explicit pilot confirmation, and reports every state transparently.

---

Pre-Flight Checklist (Mandatory before coding)

Before modifying or creating any file, the agent must validate this state and communicate it to the user:

PRE-FLIGHT E[N] · [Epic Name]
─────────────────────────────────────────────
[ ] CLAUDE.md / Base instructions read.
[ ] .knowledge/AGENT_TASKS.md reviewed for current Epic.
[ ] Style guide and architecture assimilated.
[ ] Mockups or API contracts located.
[ ] Epic/Task branch created correctly.
[ ] 'main' branch clean and up to date.
[ ] Epic dependencies and prerequisites confirmed.

FIRST TASK SELECTED: T0X · [Name]
AWAITING DEVELOPER CONFIRMATION TO START.

---

Task Lifecycle (The 5 Hybrid Gates)

Gate 0: Isolated Branching

• Action: Create or switch to a specific branch for the current task.
• Format: e[N-Epic]/t[N-Task]-[short-description] (e.g., e4/t10-ai-copilot-drawer).
• Note: If working from the IDE UI, the agent must request branch creation or warn if editing directly on main without planning.

Gate 1: Atomic, Scoped Implementation

• Action: Write code exclusively to fulfill the current task's scope (T0X).
• Restriction: Feature creep is strictly forbidden (solving next task's problems or refactoring out-of-scope code).

Gate 2: Strict Build Check (Safety Box)

• Action: Run the real production command (e.g., npm run build, cargo build). Dev mode (dev) is not sufficient.
• Block: If the build fails due to types, broken references, or compilation errors, the agent must stop immediately, fix the error, and re-run the build. Do not advance to Gate 3 without a successful build.

Gate 3: CHANGELOG Registration

• Action: Immediately document the change in CHANGELOG.md under the [Unreleased] section.
• Format: One precise bullet point per substantially modified file.

Gate 4: Formatted Commit and PR-Review

• Action: Delegate the commit message to the @commit-formatter sub-skill.
• Action 2: Run a local code audit by invoking the @pr-review sub-skill on the generated diff (git diff main...HEAD).
• Block: If the review returns REQUEST CHANGES (red/blocking findings), fix the code before sending or merging the PR.