code-ai-installer 4.0.1-a → 4.0.1-c

package/domains/development/locales/en/.agents/skills/handoff/SKILL.md

@@ -1,276 +1,276 @@
----
-name: handoff
-description: "Forming a Context Pack and assigning a task to an agent — goals, constraints, artifacts, decisions, questions, Definition of Done. Requires a standard reply format."
-type: mandatory
-domain: development
-owners:
-  - conductor
-gates:
-  - PM
-  - UX
-  - ARCH
-  - DEV
-  - REV
-  - OPS
-  - TEST
-  - RG
-tech: []
-topic:
-  - orchestration
-triggers:
-  - hand off task
-  - Context Pack
-  - agent briefing
-  - handoff format
-  - goals and constraints
-  - Definition of Done
-  - task for agent
-related:
-  - ux-discovery
-  - ux-spec
-  - ui-inventory
-  - a11y-baseline
-  - architecture-doc
-  - adr-log
-  - api-contracts
-  - data-model
-  - tdd-workflow
-  - testing-strategy-js
-  - code-review-checklist
-  - security-review
-  - performance-review-baseline
-  - deployment-ci-plan
-  - deployment-ci-plan-reference
-  - qa-test-plan
-  - qa-manual-run
-  - qa-api-contract-tests
-  - qa-security-smoke-tests
-  - release-gate
-  - release-gate-checklist-template
-  - gates
-  - board
-  - memory
-budget_lines: 280
-schema_version: 1
----
-
-
-# Skill: Context Pack Handoff
-
-Transferring tasks between gates with full context.
-
-**Sections:**
-1. [Workflow](#1-workflow)
-2. [Context Pack](#2-context-pack)
-3. [HANDOFF Envelope](#3-handoff-envelope)
-4. [Reply Format](#4-reply-format)
-5. [Gate-Specific Variations](#5-gate-specific-variations)
-6. [Example: PM→UX Handoff](#6-example-pmux-handoff)
-
----
-
-## 1. Workflow
-
-```
-1. Previous gate is completed (☑ on board)
-2. Conductor gathers the Context Pack (section 2)
-3. Conductor forms the HANDOFF Envelope (section 3)
-4. Conductor delegates to the next agent
-5. Agent receives the envelope → reads its role .md → activates skills
-6. Agent returns a response using the Reply Format (section 4)
-7. Conductor verifies the DoD → ☑ or ⚠️ (return)
-```
-
----
-
-## 2. Context Pack
-
-### Mandatory fields
-
-| Field | Description | Example |
-|-------|------------|---------|
-| **Goal** | What needs to be achieved | "Create UX Spec for Settings page" |
-| **Scope** | What is included / not included | "In: Settings CRUD. Out: Analytics" |
-| **Constraints** | Stack, deploy, deadlines, integrations | "React + Express, desktop-first" |
-| **Inputs** | Links to documents/files | "PRD: docs/prd.md, UX Discovery: ..." |
-| **Decisions** | What is already decided (cannot be changed without approval) | "ADR-001: MongoDB, ADR-002: shadcn" |
-| **Open Questions** | What is unknown | "Timer design not finalized" |
-| **DoD** | "Done" criterion | "UX Spec covers all PRD flows + states" |
-| **Output Format** | In what format to return the result | "Markdown file: docs/ux-spec.md" |
-
----
-
-## 3. HANDOFF Envelope
-
-### Template (copy as-is)
-
-```markdown
----
-## HANDOFF ENVELOPE
-
-**From:** <Gate/Agent> (e.g., PM Gate)
-**To:** <Gate/Agent> (e.g., UX/UI Designer)
-**Task ID:** <board task ID> (e.g., UX-01)
-**Date:** YYYY-MM-DD
-
-### Context Pack
-- **Goal:** <one sentence>
-- **Scope:** In: <list> | Out: <list>
-- **Constraints:** <stack, deploy, integrations>
-- **Inputs:**
-  - <file/link 1>
-  - <file/link 2>
-- **Decisions:** <key decisions that must not change>
-- **Open Questions:** <unresolved items>
-- **DoD:** <checkable criteria>
-- **Output Format:** <expected deliverable format>
-
-### Task
-- **What to do:** <concrete action>
-- **Skills to use:** $skill-1, $skill-2
-- **Acceptance criteria:**
-  - [ ] <criterion 1>
-  - [ ] <criterion 2>
----
-```
-
----
-
-## 4. Reply Format
-
-Every agent must return their deliverable in this structure:
-
-```markdown
-### Summary
-<1-3 sentences: what was done>
-
-### Deliverables
-<list of artifacts produced with paths/links>
-
-### Decisions
-<key decisions made during this gate>
-
-### Risks / Blockers
-<anything that may affect downstream gates>
-
-### Open Questions
-<unresolved items for user/conductor>
-
-### Next Actions
-<suggested next steps with IDs: UX-02, ARCH-01, etc.>
-```
-
----
-
-## 5. Gate-Specific Variations
-
-### PM → UX
-
-| Field | Typical content |
-|-------|----------------|
-| Inputs | PRD, Interview Summary |
-| Skills | $ux-discovery, $ux-spec, $ui-inventory, $a11y-baseline |
-| DoD | UX Spec covers all flows + screens + states + validations |
-
-### UX → ARCH
-
-| Field | Typical content |
-|-------|----------------|
-| Inputs | PRD, UX Spec, UI Inventory |
-| Skills | $architecture-doc, $adr-log, $api-contracts, $data-model |
-| DoD | Architecture doc + API contracts + data model + ADRs |
-
-### ARCH → DEV
-
-| Field | Typical content |
-|-------|----------------|
-| Inputs | Architecture, API Contracts, UX Spec, Data Model |
-| Skills | $tdd-workflow, $testing-strategy-js, relevant best practices |
-| DoD | Code complete, tests pass, no P0 self-review issues |
-
-### DEV → REV
-
-| Field | Typical content |
-|-------|----------------|
-| Inputs | Code diff, test results, API contracts |
-| Skills | $code-review-checklist, $security-review, $performance-review-baseline |
-| DoD | Review report with 0 P0, P1 tracked |
-
-### REV → OPS
-
-| Field | Typical content |
-|-------|----------------|
-| Inputs | Approved code, Docker config |
-| Skills | $deployment-ci-plan, /auto-restart-containers |
-| DoD | Build success, containers healthy |
-
-### OPS → TEST
-
-| Field | Typical content |
-|-------|----------------|
-| Inputs | Deployed environment, UX Spec, API Contracts |
-| Skills | $qa-test-plan, $qa-manual-run, $qa-api-contract-tests, $qa-security-smoke-tests |
-| DoD | All P0 tests pass, 0 open P0 bugs |
-
-### TEST → RG
-
-| Field | Typical content |
-|-------|----------------|
-| Inputs | All gate reports (REV, TEST, CI) |
-| Skills | $release-gate, $release-gate-checklist-template |
-| DoD | Release checklist complete, GO decision |
-
----
-
-## 6. Example: PM→UX Handoff
-
-```markdown
----
-## HANDOFF ENVELOPE
-
-**From:** PM Gate (PM Agent)
-**To:** UX/UI Designer
-**Task ID:** UX-01
-**Date:** 2026-03-13
-
-### Context Pack
-- **Goal:** Create UX Spec for SaaS Admin Panel Dashboard
-- **Scope:** In: Settings, Products, Content preview | Out: Analytics, multi-lang
-- **Constraints:** React + Express, desktop-first, shadcn/ui components
-- **Inputs:**
-  - PRD: `docs/prd.md`
-  - Backlog: `docs/backlog.md`
-- **Decisions:** ADR-001: MongoDB for storage, ADR-002: shadcn/ui for UI
-- **Open Questions:** Notification design (email vs in-app)
-- **DoD:** UX Spec covers all 5 PRD user stories, all screens have 4 states
-- **Output Format:** `docs/ux-spec.md`
-
-### Task
-- **What to do:** Run $ux-discovery → $ux-spec → $ui-inventory → $a11y-baseline
-- **Skills to use:** $ux-discovery, $ux-spec, $ui-inventory, $a11y-baseline
-- **Acceptance criteria:**
-  - [ ] All PRD flows have screen specs
-  - [ ] States: loading/empty/error/success defined per screen
-  - [ ] UI Inventory maps to design system components
-  - [ ] A11y baseline documented
----
-```
-
----
-
-## Common handoff-document rules (cross-domain)
-
-> Applies to **any** handoff document written to hand the session over to a fresh agent (session-handoff / conversation summary). Supplements, does not replace, the inter-gate handoff sections above.
-
-1. **Where to save.** The handoff document goes to the **OS temp directory** (`%TEMP%` / `/tmp` / `os.tmpdir()`), **not** the working repository. Workspace stays clean; the path to the temp file is cited in the next session's chat.
-2. **"Suggested skills" section.** The document MUST include a section listing the skills the fresh agent should invoke first (`$skill-1`, `$skill-2`, ...). This shortens context warm-up.
-3. **Do not duplicate artifacts.** If the data is already in a PRD / plan / ADR / commit / diff / issue — link to it by **path or URL**, do not copy the content. Duplication causes drift between sources.
-4. **Redact sensitive data.** Before saving, strip API keys, passwords, tokens, PII (email, phone, real customer names). The temp directory is also a potential leak vector.
-5. **User arguments = next-session focus.** If `/handoff` is called with an argument string, treat it as a description of the next session's task; tailor the summary and suggested-skills list to that focus.
-
----
-
-## See also
-- `$gates` — gate definitions and DoD
-- `$board` — project board tracking
-- `$memory` — context preservation
+---
+name: handoff
+description: "Forming a Context Pack and assigning a task to an agent — goals, constraints, artifacts, decisions, questions, Definition of Done. Requires a standard reply format."
+type: mandatory
+domain: development
+owners:
+  - conductor
+gates:
+  - PM
+  - UX
+  - ARCH
+  - DEV
+  - REV
+  - OPS
+  - TEST
+  - RG
+tech: []
+topic:
+  - orchestration
+triggers:
+  - hand off task
+  - Context Pack
+  - agent briefing
+  - handoff format
+  - goals and constraints
+  - Definition of Done
+  - task for agent
+related:
+  - ux-discovery
+  - ux-spec
+  - ui-inventory
+  - a11y-baseline
+  - architecture-doc
+  - adr-log
+  - api-contracts
+  - data-model
+  - tdd-workflow
+  - testing-strategy-js
+  - code-review-checklist
+  - security-review
+  - performance-review-baseline
+  - deployment-ci-plan
+  - deployment-ci-plan-reference
+  - qa-test-plan
+  - qa-manual-run
+  - qa-api-contract-tests
+  - qa-security-smoke-tests
+  - release-gate
+  - release-gate-checklist-template
+  - gates
+  - board
+  - memory
+budget_lines: 280
+schema_version: 1
+---
+
+
+# Skill: Context Pack Handoff
+
+Transferring tasks between gates with full context.
+
+**Sections:**
+1. [Workflow](#1-workflow)
+2. [Context Pack](#2-context-pack)
+3. [HANDOFF Envelope](#3-handoff-envelope)
+4. [Reply Format](#4-reply-format)
+5. [Gate-Specific Variations](#5-gate-specific-variations)
+6. [Example: PM→UX Handoff](#6-example-pmux-handoff)
+
+---
+
+## 1. Workflow
+
+```
+1. Previous gate is completed (☑ on board)
+2. Conductor gathers the Context Pack (section 2)
+3. Conductor forms the HANDOFF Envelope (section 3)
+4. Conductor delegates to the next agent
+5. Agent receives the envelope → reads its role .md → activates skills
+6. Agent returns a response using the Reply Format (section 4)
+7. Conductor verifies the DoD → ☑ or ⚠️ (return)
+```
+
+---
+
+## 2. Context Pack
+
+### Mandatory fields
+
+| Field | Description | Example |
+|-------|------------|---------|
+| **Goal** | What needs to be achieved | "Create UX Spec for Settings page" |
+| **Scope** | What is included / not included | "In: Settings CRUD. Out: Analytics" |
+| **Constraints** | Stack, deploy, deadlines, integrations | "React + Express, desktop-first" |
+| **Inputs** | Links to documents/files | "PRD: docs/prd.md, UX Discovery: ..." |
+| **Decisions** | What is already decided (cannot be changed without approval) | "ADR-001: MongoDB, ADR-002: shadcn" |
+| **Open Questions** | What is unknown | "Timer design not finalized" |
+| **DoD** | "Done" criterion | "UX Spec covers all PRD flows + states" |
+| **Output Format** | In what format to return the result | "Markdown file: docs/ux-spec.md" |
+
+---
+
+## 3. HANDOFF Envelope
+
+### Template (copy as-is)
+
+```markdown
+---
+## HANDOFF ENVELOPE
+
+**From:** <Gate/Agent> (e.g., PM Gate)
+**To:** <Gate/Agent> (e.g., UX/UI Designer)
+**Task ID:** <board task ID> (e.g., UX-01)
+**Date:** YYYY-MM-DD
+
+### Context Pack
+- **Goal:** <one sentence>
+- **Scope:** In: <list> | Out: <list>
+- **Constraints:** <stack, deploy, integrations>
+- **Inputs:**
+  - <file/link 1>
+  - <file/link 2>
+- **Decisions:** <key decisions that must not change>
+- **Open Questions:** <unresolved items>
+- **DoD:** <checkable criteria>
+- **Output Format:** <expected deliverable format>
+
+### Task
+- **What to do:** <concrete action>
+- **Skills to use:** $skill-1, $skill-2
+- **Acceptance criteria:**
+  - [ ] <criterion 1>
+  - [ ] <criterion 2>
+---
+```
+
+---
+
+## 4. Reply Format
+
+Every agent must return their deliverable in this structure:
+
+```markdown
+### Summary
+<1-3 sentences: what was done>
+
+### Deliverables
+<list of artifacts produced with paths/links>
+
+### Decisions
+<key decisions made during this gate>
+
+### Risks / Blockers
+<anything that may affect downstream gates>
+
+### Open Questions
+<unresolved items for user/conductor>
+
+### Next Actions
+<suggested next steps with IDs: UX-02, ARCH-01, etc.>
+```
+
+---
+
+## 5. Gate-Specific Variations
+
+### PM → UX
+
+| Field | Typical content |
+|-------|----------------|
+| Inputs | PRD, Interview Summary |
+| Skills | $ux-discovery, $ux-spec, $ui-inventory, $a11y-baseline |
+| DoD | UX Spec covers all flows + screens + states + validations |
+
+### UX → ARCH
+
+| Field | Typical content |
+|-------|----------------|
+| Inputs | PRD, UX Spec, UI Inventory |
+| Skills | $architecture-doc, $adr-log, $api-contracts, $data-model |
+| DoD | Architecture doc + API contracts + data model + ADRs |
+
+### ARCH → DEV
+
+| Field | Typical content |
+|-------|----------------|
+| Inputs | Architecture, API Contracts, UX Spec, Data Model |
+| Skills | $tdd-workflow, $testing-strategy-js, relevant best practices |
+| DoD | Code complete, tests pass, no P0 self-review issues |
+
+### DEV → REV
+
+| Field | Typical content |
+|-------|----------------|
+| Inputs | Code diff, test results, API contracts |
+| Skills | $code-review-checklist, $security-review, $performance-review-baseline |
+| DoD | Review report with 0 P0, P1 tracked |
+
+### REV → OPS
+
+| Field | Typical content |
+|-------|----------------|
+| Inputs | Approved code, Docker config |
+| Skills | $deployment-ci-plan + Docker restart (AGENTS.md rule) |
+| DoD | Build success, containers healthy |
+
+### OPS → TEST
+
+| Field | Typical content |
+|-------|----------------|
+| Inputs | Deployed environment, UX Spec, API Contracts |
+| Skills | $qa-test-plan, $qa-manual-run, $qa-api-contract-tests, $qa-security-smoke-tests |
+| DoD | All P0 tests pass, 0 open P0 bugs |
+
+### TEST → RG
+
+| Field | Typical content |
+|-------|----------------|
+| Inputs | All gate reports (REV, TEST, CI) |
+| Skills | $release-gate, $release-gate-checklist-template |
+| DoD | Release checklist complete, GO decision |
+
+---
+
+## 6. Example: PM→UX Handoff
+
+```markdown
+---
+## HANDOFF ENVELOPE
+
+**From:** PM Gate (PM Agent)
+**To:** UX/UI Designer
+**Task ID:** UX-01
+**Date:** 2026-03-13
+
+### Context Pack
+- **Goal:** Create UX Spec for SaaS Admin Panel Dashboard
+- **Scope:** In: Settings, Products, Content preview | Out: Analytics, multi-lang
+- **Constraints:** React + Express, desktop-first, shadcn/ui components
+- **Inputs:**
+  - PRD: `docs/prd.md`
+  - Backlog: `docs/backlog.md`
+- **Decisions:** ADR-001: MongoDB for storage, ADR-002: shadcn/ui for UI
+- **Open Questions:** Notification design (email vs in-app)
+- **DoD:** UX Spec covers all 5 PRD user stories, all screens have 4 states
+- **Output Format:** `docs/ux-spec.md`
+
+### Task
+- **What to do:** Run $ux-discovery → $ux-spec → $ui-inventory → $a11y-baseline
+- **Skills to use:** $ux-discovery, $ux-spec, $ui-inventory, $a11y-baseline
+- **Acceptance criteria:**
+  - [ ] All PRD flows have screen specs
+  - [ ] States: loading/empty/error/success defined per screen
+  - [ ] UI Inventory maps to design system components
+  - [ ] A11y baseline documented
+---
+```
+
+---
+
+## Common handoff-document rules (cross-domain)
+
+> Applies to **any** handoff document written to hand the session over to a fresh agent (session-handoff / conversation summary). Supplements, does not replace, the inter-gate handoff sections above.
+
+1. **Where to save.** The handoff document goes to the **OS temp directory** (`%TEMP%` / `/tmp` / `os.tmpdir()`), **not** the working repository. Workspace stays clean; the path to the temp file is cited in the next session's chat.
+2. **"Suggested skills" section.** The document MUST include a section listing the skills the fresh agent should invoke first (`$skill-1`, `$skill-2`, ...). This shortens context warm-up.
+3. **Do not duplicate artifacts.** If the data is already in a PRD / plan / ADR / commit / diff / issue — link to it by **path or URL**, do not copy the content. Duplication causes drift between sources.
+4. **Redact sensitive data.** Before saving, strip API keys, passwords, tokens, PII (email, phone, real customer names). The temp directory is also a potential leak vector.
+5. **User arguments = next-session focus.** If `/handoff` is called with an argument string, treat it as a description of the next session's task; tailor the summary and suggested-skills list to that focus.
+
+---
+
+## See also
+- `$gates` — gate definitions and DoD
+- `$board` — project board tracking
+- `$memory` — context preservation