@polymorphism-tech/morph-spec 4.22.0 → 6.0.0

package/framework/commands/morph-apply.md

@@ -1,240 +1,56 @@
----
-description: Implement the specified feature following the task breakdown from the MORPH-SPEC workflow. Orchestrates task execution with state tracking, checkpoints, agent dispatch, and verification.
-argument-hint: <feature-name>
-allowed-tools: Read, Write, Edit, Bash, Glob, Grep, Agent, AskUserQuestion
----
-
-# /morph-apply — Feature Implementation
-
-Implement the feature by executing its task breakdown, tracking progress through the morph-spec state machine, and producing a recap at the end.
-
-## Usage
-
-```
-/morph-apply {feature-name}
-```
-
-## Recommended Tools
-
-> **Ref:** `framework/skills/level-0-meta/morph-tool-usage-guide/SKILL.md` for complete guide.
-> **Ref:** `framework/standards/integration/mcp/mcp-tools.md` for MCP reference.
-
-| Action | Tool | Alternative |
-|--------|------|-------------|
-| Read spec, tasks, contracts | **Read** all outputs | — |
-| Detect architecture style | **Bash** `cat .morph/config/config.json \| grep architecture` | — |
-| Agent dispatch config | **Bash** `morph-spec dispatch-agents $ARGUMENTS implement` | — |
-| Parallel task execution | **Agent** subagent per task group | Sequential fallback |
-| Look up implementation patterns | **Context7 MCP** `query_docs()` | **WebSearch** |
-| Track progress | **Bash** `morph-spec state get $ARGUMENTS` | — |
-
----
-
-## Pre-flight Validation
-
-Before writing any code, verify all prior phases are complete. This gate prevents implementation from starting with missing specs, unapproved designs, or incomplete task breakdowns.
-
-### 1. Check state and approvals
-
-```bash
-morph-spec state get $ARGUMENTS
-morph-spec approval-status $ARGUMENTS
-morph-spec validate-feature $ARGUMENTS
-```
-
-**All three must pass.** If any fails:
-
-```
-Feature is not ready for implementation.
-Run /morph-proposal $ARGUMENTS to complete planning phases.
-(Resumes automatically from the current phase.)
-```
-
-Do NOT proceed until all phases are complete and all gates approved.
-
-### 2. Load context in PARALLEL
-
-Read all prerequisite files in a single parallel call — every file listed here matters for implementation quality:
-
-```
-Read: .morph/features/$ARGUMENTS/2-design/spec.md              (→ functional requirements, API contracts)
-    + Read: .morph/features/$ARGUMENTS/2-design/contracts.cs    (or contracts.ts / contracts-vsa.cs → C# interfaces)
-    + Read: .morph/features/$ARGUMENTS/2-design/decisions.md    (→ ADRs, architectural choices)
-    + Read: .morph/features/$ARGUMENTS/3-plan/plan.md           (→ TDD structure, execution strategy)
-    + Read: .morph/features/$ARGUMENTS/4-tasks/tasks.md         (→ task breakdown with T### IDs)
-    + Read: .morph/config/config.json                           (→ architecture.style for VSA routing)
-```
-
-**For VSA projects** (`architecture.style: "vertical-slice"`), also read:
-```
-Read: framework/standards/architecture/vertical-slice/vertical-slice.md
-```
-This contains the 9 VSA implementation rules (Handler+Validator+Endpoint per feature folder, no cross-feature imports, etc.).
-
-Also read relevant standards:
-- `framework/standards/` — coding standards for the detected stack
-- `.morph/context/` — project-specific patterns and conventions
-
-### 3. Detect architecture style
-
-```bash
-cat .morph/config/config.json | grep -A3 '"architecture"'
-```
-
-- **`"vertical-slice"`** → follow VSA implementation patterns from `framework/standards/architecture/vertical-slice/vertical-slice.md`. Each task is a complete slice (Handler + Validator + Endpoint in one folder).
-
-### 4. Get agent dispatch config
-
-```bash
-morph-spec dispatch-agents $ARGUMENTS implement --table
-```
-
-This shows which agents are active for implementation and how tasks can be grouped. If agent teams are enabled and tasks have no dependencies between groups, consider dispatching parallel agents:
-
-```bash
-morph-spec dispatch-agents $ARGUMENTS implement
-```
-
-The JSON output includes `shouldDispatch`, `recommended` (agents by group), and `tasks` (task IDs by group) for multi-agent coordination.
-
----
-
-## Workflow
-
-### Step 1: Advance to implement phase
-
-```bash
-morph-spec phase advance $ARGUMENTS
-```
-
-This validates phase eligibility and emits a SKILL DISPATCH block listing required skills for implementation (verification-before-completion, morph-checklist, etc.).
-
-### Step 1.5: Create pipeline visibility task
-
-> **MANDATORY** — Create umbrella task for implementation tracking.
-
-```
-TaskCreate: "Implement: {feature-name}"
-  → description: "Execute T001-T00N from tasks.md with checkpoints"
-  → activeForm: "Implementing feature"
-```
-
-Mark as `in_progress`. After all tasks complete (Step 5), mark as `completed`.
-
-### Step 2: Initialize state tracking
-
-```bash
-morph-spec state set $ARGUMENTS tasks.total {N}
-```
-
-Where `{N}` is the number of tasks in tasks.md (e.g., 6 for T001-T006).
-
-### Step 3: Execute tasks in order
-
-For each task in the breakdown, follow this cycle:
-
-```bash
-# 1. Start the task (activates task-tracking guard)
-morph-spec task start $ARGUMENTS {task-id}
-
-# 2. Implement the task
-#    - Follow spec.md and contracts
-#    - Follow coding standards from framework/standards/ and .morph/context/
-#    - For VSA: create all slice files in one folder (Handler + Validator + Endpoint)
-
-# 3. Verify before completing — run validate-feature or check your work
-#    matches the spec and contracts before marking done
-
-# 4. Complete the task (triggers Tier-4 validators automatically)
-morph-spec task done $ARGUMENTS {task-id}
-```
-
-**If validation fails on `task done`:**
-- Read the error messages carefully
-- Fix the violations in your code
-- Re-run `task done` — do NOT use `--skip-validation` unless the user explicitly authorizes it
-- After 3 consecutive failures, escalate to the user
-
-**`--skip-validation` budget system:**
-- Budget-limited: `min(5, ceil(totalTasks × 0.20))` — e.g., 5 tasks → 1 skip, 32 tasks → 5 skips
-- Requires `--reason <text>` (minimum 5 characters) for audit trail
-- Skipped tasks don't count as `passed` in validationHistory → degrades pass rate
-- Usage: `morph-spec task done feat T001 --skip-validation --reason "CSS-only change, no logic"`
-- When budget is exhausted, all remaining tasks must pass Tier-4 validation
-
-**Parallel execution (agent teams):**
-If `dispatch-agents` identified parallelizable task groups and agent teams are enabled, dispatch independent tasks to separate agents. Each agent still calls `task start` and `task done` for its assigned task.
-
-### Step 4: Checkpoint every 3 tasks
-
-After every 3 completed tasks, save a checkpoint:
-
-```bash
-morph-spec checkpoint-save $ARGUMENTS "after-T003"
-morph-spec state get $ARGUMENTS
-```
-
-Checkpoints validate architecture compliance, check package versions, scan for security issues, and save a restorable snapshot. The cadence is every 3 tasks — for 6 tasks: checkpoint after T003 and T006. For 10 tasks: after T003, T006, T009, and at completion.
-
-After each checkpoint, check progress:
-
-```bash
-morph-spec state list
-```
-
-### Step 5: Finalize implementation
-
-After all tasks are complete:
-
-```bash
-# Final validation
-morph-spec validate-feature $ARGUMENTS
-
-# Generate recap (auto-marks 'recap' output in state)
-morph-spec generate recap $ARGUMENTS
-
-# Verify final state
-morph-spec state get $ARGUMENTS
-
-# Advance to next phase
-morph-spec phase advance $ARGUMENTS
-```
-
-### Step 6: Post-implementation review
-
-After implementation, present a summary to the user:
-
-1. Total tasks completed (X/Y)
-2. Files created/modified
-3. Validation results
-4. Any deviations from spec
-
-For Azure projects, remind the user: "Run `/morph-preflight` before deploying to validate packages, migrations, Docker, and secrets."
-
----
-
-## Task Output Format
-
-After each task completion, show:
-
-```
-Task {task-id} complete (X/Y tasks done)
-Files: [list of created/modified files]
-Next: {next-task-id} — {next-task-title}
-```
-
----
-
-## Anti-patterns
-
-- Using `state set phase` instead of `phase advance` — phase advance validates eligibility first
-- Skipping `task start` before implementing — the task-tracking guard will warn
-- Using `--skip-validation` without user authorization or without `--reason`
-- Exhausting `--skip-validation` budget on trivial tasks — reserve for genuine emergencies
-- Implementing without reading spec.md and contracts first
-- Writing code before `phase advance` to implement — the hook will block writes
-- Skipping checkpoints — they catch integration issues early
-
----
-
-**Feature:** $ARGUMENTS
+---
+description: Implementa a feature aprovada no Gate 2. Loop autônomo de tarefas via morph-implement com auto-advance entre tarefas, depois morph-review apresenta o Gate 3.
+argument-hint: <feature-name>
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep, Agent, AskUserQuestion, Skill
+---
+
+# /morph-apply — NLH Implementation
+
+Executa as tarefas do `tasks.md` em sequência sem pausa, depois apresenta o Gate 3.
+
+## Argumentos
+
+`{feature-name}` — nome da feature já planejada (Gate 2 aprovado).
+
+## Pré-requisitos
+
+Antes de começar, verifique:
+- `.morph/features/{feature-name}/2-plan/spec.md` existe
+- `.morph/features/{feature-name}/2-plan/mandate.md` existe
+- `.morph/features/{feature-name}/2-plan/tasks.md` existe
+- `.morph/features/{feature-name}/3-implement/recap.md` existe ou pode ser criado
+
+Se algum estiver faltando, abortar e pedir ao usuário para rodar `/morph-proposal {feature-name}` primeiro.
+
+## Fluxo
+
+1. **Loop de tarefas** — para cada tarefa pendente em `tasks.md`:
+   - Invocar a skill `morph-implement` em `framework/skills/core/morph-implement/`.
+   - A skill executa a tarefa, registra em `recap.md`, atualiza o trace.
+   - **Auto-advance:** ao concluir uma tarefa, passar imediatamente para a próxima sem aguardar instrução do usuário.
+   - Pausar apenas se encontrar ambiguidade bloqueante não coberta pelo `mandate.md`.
+
+2. **Após todas as tarefas concluídas, invocar `morph-review`** (skill em `framework/skills/core/morph-review/`):
+   - Lê `mandate.md` e `recap.md`.
+   - Aplica `morph-eval` para gerar scores por dimensão.
+   - Produz `review-report.md` em `.morph/features/{feature-name}/4-review/`.
+   - Apresenta o **Gate 3**.
+
+3. **Aguardar aprovação do Gate 3.**
+   - Resposta válida: "aprovado", "merge".
+   - Se houver itens bloqueantes (score < 6): corrija antes de apresentar o gate.
+
+## Anti-padrões
+
+- Não pausar entre tarefas para confirmação — o tasks.md já foi aprovado no Gate 2.
+- Não escrever código fora de `3-implement/` ou da source tree do projeto.
+- Não modificar `spec.md` ou `mandate.md` durante a implementação — esses arquivos foram congelados pelo Gate 2.
+
+## Referências
+
+- `framework/MORPH.md` — charter completo
+- `framework/skills/core/morph-implement/SKILL.md`
+- `framework/skills/core/morph-eval/SKILL.md`
+- `framework/skills/core/morph-review/SKILL.md`
+
+**Feature:** $ARGUMENTS

package/framework/commands/morph-archive.md

@@ -1,85 +1,48 @@
----
-description: Archive a completed feature by moving from features/ to archive/ and updating state
-argument-hint: <feature-name>
-allowed-tools: Read, Write, Edit, Bash
----
-
-# Archive MORPH Feature
-
-Archive a completed feature, moving it from `features/` to `archive/`.
-
-## Prerequisites
-
-Verify before archiving:
-- [ ] Feature exists in `.morph/features/{feature}/`
-- [ ] All tasks are complete
-- [ ] `recap.md` is filled in
-- [ ] Code is in production (or staging)
-
-## Workflow
-
-1. **Validate completion**:
-   - Read `.morph/features/{feature}/4-tasks/tasks.md`
-   - Verify all tasks are completed
-   - Confirm with user before archiving
-
-2. **Complete the recap**:
-   - Update `.morph/features/{feature}/5-implement/recap.md`
-   - Fill in final metrics
-   - Document lessons learned
-
-3. **Extract specs**:
-   - If the feature defines permanent behavior
-   - Copy relevant spec to `.morph/specs/`
-   - This becomes the "current truth" of the system
-
-4. **Move to archive**:
-   ```
-   .morph/features/{feature}/  →  .morph/archive/{feature}/
-   ```
-
-5. **Update project metrics**:
-   - Increment feature counter
-   - Update total cost
-   - Update total time
-
-## Output
-
-Present archival summary:
-
-```
-╔════════════════════════════════════════════╗
-║         FEATURE ARCHIVED                   ║
-╠════════════════════════════════════════════╣
-║ Feature: {name}                            ║
-║ Completed: {date}                          ║
-╠════════════════════════════════════════════╣
-║ METRICS                                    ║
-╠════════════════════════════════════════════╣
-║ Tasks: {X}/{X} completed                   ║
-║ Time: {X}h (estimated: {Y}h)               ║
-║ Cost Impact: +${X}/month                   ║
-╠════════════════════════════════════════════╣
-║ FILES                                      ║
-╠════════════════════════════════════════════╣
-║ Created: {X} files                         ║
-║ Modified: {Y} files                        ║
-║ Tests: {Z} files ({W}% coverage)           ║
-╠════════════════════════════════════════════╣
-║ ARCHIVED TO                                ║
-╠════════════════════════════════════════════╣
-║ .morph/archive/{feature}/                  ║
-╚════════════════════════════════════════════╝
-```
-
-## Extracted Specs
-
-If specs were extracted:
-```
-Specs extracted to .morph/specs/:
-- {domain}/spec.md - {description}
-```
-
----
-
-**Feature to archive:** $ARGUMENTS
+---
+description: Archive a completed MORPH-SPEC feature after Gate 3 approval
+argument-hint: <feature-name>
+allowed-tools: Read, Write, Edit, Bash
+---
+
+# Archive MORPH Feature
+
+Archive a feature that has cleared Gate 3 (review). Use when the work is shipped and you want the
+feature out of the active set in `.morph/features/`.
+
+## Prerequisites
+
+Before archiving, verify:
+- [ ] Feature folder exists at `.morph/features/{feature}/`
+- [ ] `4-review/review-report.md` exists and Gate 3 is approved in `state.json`
+- [ ] `3-implement/recap.md` is filled in
+- [ ] Code is merged or otherwise shipped
+
+If any precondition fails, stop and report what is missing instead of archiving.
+
+## Workflow
+
+1. **Validate completion** by reading `state.json`:
+   - `features[name].phase === 'review'`
+   - `features[name].approvalGates.review.approved === true`
+
+2. **Move the folder** from active to archive:
+   ```
+   .morph/features/{feature}/  →  .morph/archive/{feature}/
+   ```
+   Use `Bash` (`mv` on POSIX, `Move-Item` on Windows). Preserve all phase subfolders
+   (`0-proposal/`, `1-ui/`, `2-plan/`, `3-implement/`, `4-review/`).
+
+3. **Update state.json**:
+   - Set `features[name].status = 'completed'`
+   - Set `features[name].archivedAt = <ISO timestamp>`
+
+4. **Confirm with the user** before any destructive step. Show the move plan first.
+
+## Output
+
+Present a short summary of what moved and the new path. Do not invent metrics that are not
+recorded in state.json or recap.md.
+
+---
+
+**Feature to archive:** $ARGUMENTS

package/framework/commands/morph-preflight.md

@@ -26,18 +26,18 @@ These checks verify that the morph-spec workflow is complete for the feature bei
 
 ```bash
 # Verify implementation is complete
-morph-spec state get {feature}
+morph-spec status {feature}
 morph-spec approval-status {feature}
-morph-spec validate-feature {feature}
+morph-spec validate {feature}
 ```
 
 | Check | Command | Pass Criteria |
 |-------|---------|---------------|
-| Phase is implement or later | `state get` | phase derived as `implement` |
-| All gates approved | `approval-status` | design, plan, tasks gates all approved |
-| Feature validation passes | `validate-feature` | 100% pass rate |
-| All tasks complete | `state get` → tasks | 0 tasks in `pending` or `in_progress` |
-| Recap generated | Read `5-implement/recap.md` | File exists and is non-empty |
+| Phase is implement or later | `status` | phase derived as `implement` or `review` |
+| All gates approved | `approval-status` | proposal, plan, review gates all approved |
+| Feature validation passes | `validate` | 100% pass rate |
+| All tasks complete | `status` → tasks | 0 tasks in `pending` or `in_progress` |
+| Recap generated | Read `3-implement/recap.md` | File exists and is non-empty |
 
 **If any MORPH check fails:** Show which check failed and recommend: `Run /morph-apply {feature} to complete implementation before deploying.`