@relipa/ai-flow-kit 0.0.4-beta.3 → 0.0.5-beta.0

package/custom/templates/shared/gate-workflow.md

@@ -1,75 +1,88 @@
-## MANDATORY: Strict Gate Workflow
-
-> **Absolute Rule: Complete Gate N before entering Gate N+1.**
-> **Do not skip, shorten, or merge Gates.**
-
-You have superpowers. When a ticket context exists in `.aiflow/context/current.json`:
-- **AUTO-START Gate 1 immediately** — do NOT wait for the developer to ask.
-- Read instructions and follow the gate sequence below — NO EXCEPTIONS.
-
----
-
-### GATE 1 — AI Analyze Requirement (auto-start)
-
-**INVOKE:** `validate-ticket` skill
-
-AI actively reads ticket + source code to understand the requirement:
-1. Read `.aiflow/context/current.json` — ticket info
-2. Read source code — architecture, related files, data flow
-3. If anything is unclear — ask ONE question at a time, wait for reply
-4. Output `plan/[ticket-id]/requirement.md` with:
-   - Requirements summary, source code analysis
-   - Proposed solution and approach
-   - Impact analysis, effort estimate, testing plan
-5. Display "GATE 1: Requirement doc ready" → wait for **APPROVED**
-
-> [!TIP]
-> If auto-start doesn't trigger, the developer can start this gate by typing: **"start"**, **"Gate 1"** or **"Analyze ticket"**.
-
-DO NOT just check format — **understand the content and propose solutions**.
-
----
-
-### GATE 2 — Implementation Plan (wait for APPROVED)
-
-**INVOKE:** `generate-spec` skill, then `superpowers:writing-plans`
-
-- Create a detailed TDD implementation plan based on the approved requirement.
-- Display: "GATE 2 PAUSED: type APPROVED to start coding".
-- CODE WILL NOT BE GENERATED until "APPROVED" is received.
-
----
-
-### GATE 3 — Code Generation (TDD only)
-
-Only runs after Gate 2 has been APPROVED.
-
-**INVOKE:** `superpowers:test-driven-development`
-- Complex feature (3+ files): `superpowers:subagent-driven-development`
-- Write tests FIRST — run to confirm FAIL -> implement -> PASS.
-- Bug fix EXTRA: `superpowers:systematic-debugging` + `investigate-bug` skill first.
-
----
-
-### GATE 4 — AI Self-Review (wait for APPROVED)
-
-**INVOKE:** `review-plan` skill
-
-Mandatory order:
-1. `superpowers:verification-before-completion` — all tests must PASS
-2. `impact-analysis` skill — check for breaking changes
-3. Tick `custom/rules/review-checklist.md`
-4. Create `plan/[ticket-id]/summary.md`
-
-Then: "GATE 4 PAUSED: type APPROVED or BUG: [description]"
-- Coding bug -> fix -> repeat Gate 4.
-- Requirement bug -> return to Gate 1.
-
----
-
-### GATE 5 — Peer Review and Done
-
-Only runs after Gate 4 has been APPROVED.
-
-**INVOKE:** `superpowers:requesting-code-review`
-Guide on creating a Pull Request with the ticket link.
+## MANDATORY: Strict Gate Workflow
+
+> **Absolute Rule: Complete Gate N before entering Gate N+1.**
+> **Do not skip, shorten, or merge Gates.**
+
+You have superpowers. When a ticket context exists in `.aiflow/context/current.json`:
+- **Consult the "AI Skill Registry"** below to find instructions for each skill (`SKILL.md`).
+- **AUTO-START Gate 1 immediately** — do NOT wait for the developer to ask.
+- Read instructions and follow the gate sequence below — NO EXCEPTIONS.
+
+---
+
+### GATE 1 — AI Analyze Requirement (auto-start)
+
+**INVOKE:** `validate-ticket` skill
+
+AI actively reads ticket + source code to understand the requirement:
+1. Read `.aiflow/context/current.json` — ticket info
+2. Read source code — architecture, related files, data flow
+3. If anything is unclear — ask ONE question at a time, wait for reply
+4. Output `plan/[ticket-id]/requirement.md` with:
+   - Requirements summary, source code analysis
+   - Proposed solution and approach
+   - Impact analysis, effort estimate, testing plan
+5. Display "GATE 1: Requirement doc ready" → wait for **APPROVED**
+
+> **Tip:** If auto-start doesn't trigger, the developer can start this gate by typing: **"start"**, **"Gate 1"** or **"Analyze ticket"**.
+
+DO NOT just check format — **understand the content and propose solutions**.
+
+> **Telemetry:** Run `aiflow gate 1 start --ticket [ticket-id]` when starting this gate (auto-start or when developer types "start"/"Gate 1").
+> Run `aiflow gate 1 approved --ticket [ticket-id]` immediately when APPROVED is received.
+
+---
+
+### GATE 2 — Implementation Plan (wait for APPROVED)
+
+**INVOKE:** `generate-spec` skill, then `superpowers:writing-plans`
+
+- Create a detailed TDD implementation plan based on the approved requirement.
+- Display: "GATE 2 PAUSED: type APPROVED to start coding".
+- CODE WILL NOT BE GENERATED until "APPROVED" is received.
+
+> **Telemetry:** Run `aiflow gate 2 start --ticket [ticket-id]` when starting this gate.
+> Run `aiflow gate 2 approved --ticket [ticket-id]` immediately when APPROVED is received.
+
+---
+
+### GATE 3 — Code Generation (TDD only)
+
+Only runs after Gate 2 has been APPROVED.
+
+**INVOKE:** `superpowers:test-driven-development`
+- Complex feature (3+ files): `superpowers:subagent-driven-development`
+- Write tests FIRST — run to confirm FAIL -> implement -> PASS.
+- Bug fix EXTRA: `superpowers:systematic-debugging` + `investigate-bug` skill first.
+
+> **Telemetry:** Run `aiflow gate 3 start --ticket [ticket-id]` when starting this gate.
+
+---
+
+### GATE 4 — AI Self-Review (wait for APPROVED)
+
+**INVOKE:** `review-plan` skill
+
+Mandatory order:
+1. `superpowers:verification-before-completion` — all tests must PASS
+2. `impact-analysis` skill — check for breaking changes
+3. Tick `custom/rules/review-checklist.md`
+4. Create `plan/[ticket-id]/summary.md`
+
+Then: "GATE 4 PAUSED: type APPROVED or BUG: [description]"
+- Coding bug -> fix -> repeat Gate 4.
+- Requirement bug -> return to Gate 1.
+
+> **Telemetry:** Run `aiflow gate 4 start --ticket [ticket-id]` when starting this gate.
+> Run `aiflow gate 4 approved --ticket [ticket-id]` immediately when APPROVED is received.
+
+---
+
+### GATE 5 — Peer Review and Done
+
+Only runs after Gate 4 has been APPROVED.
+
+**INVOKE:** `superpowers:requesting-code-review`
+Guide on creating a Pull Request with the ticket link.
+
+> **Telemetry:** Run `aiflow gate 5 start --ticket [ticket-id]` when starting this gate.