@polymorphism-tech/morph-spec 4.13.0 → 4.14.0

package/framework/commands/morph-proposal.md

@@ -1,238 +1,210 @@
----
-description: MORPH Spec Pipeline — creates or resumes feature planning through phases 0-8 with mandatory approval pauses. Use whenever the user wants to plan, spec, or design a new feature, or when they say /morph-proposal. This is the primary entry point for all MORPH-SPEC feature work.
-argument-hint: <feature-name>
-allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
----
-
-# MORPH Spec Pipeline
-
-Guide a feature through the full planning pipeline (proposal through tasks) with mandatory approval pauses at each gate.
-
----
-
-## 1. Resume Logic
-
-Check if the feature already has state:
-
-```bash
-morph-spec state get {feature-name}
-```
-
-- **Exists:** Read the current phase and resume from where it stopped (skip completed phases). Create pipeline master tasks (Step 6) and mark already-completed phases as `completed`.
-- **Does not exist:** Start from scratch (PHASE 0)
-
----
-
-## 2. PHASE 0: PROPOSAL
-
-### Step 1: Load project context
-
-Read these files to understand the project before writing anything:
-- `.morph/context/README.md` — project overview, tech stack, architecture
-- `.morph/config/config.json` — project configuration (language, workflow, architecture style)
-
-### Step 2: Detect agents
-
-Read `framework/agents.json` (or `.morph/framework/agents.json` in client projects). For each agent:
-1. Check if `always_active: true` — include automatically
-2. Compare agent `keywords[]` and `domains[]` against the feature description — include on match
-3. **Document false-positive exclusions**: for agents that match on keywords but are irrelevant to this feature, note why they were excluded (this helps audit agent selection later)
-
-Register each selected agent:
-```bash
-morph-spec state add-agent {feature-name} {agent-id}
-```
-
-### Step 3: Determine if UI/UX phase is needed
-
-If `ui-designer` is among the selected agents, the feature will trigger the UI/UX phase later. Note this decision — it affects the pipeline path.
-
-### Step 4: Create proposal
-
-Read the proposal template at `framework/templates/docs/proposal.md` first, then create:
-
-```
-.morph/features/{feature-name}/
-  0-proposal/proposal.md
-```
-
-Fill every section of the template. In particular:
-- **Metadata table**: date, author, status, priority, stack
-- **Problem Statement**: use the What/Who/Impact structure from the template
-- **Proposed Solution**: technical approach, key features, user journey
-- **Success Metrics**: quantified current vs target values
-- **Scope**: explicit In Scope, Out of Scope, and Future Considerations
-- **Risks**: table with likelihood, impact, mitigation
-- **Dependencies**: checklist of prerequisites
-- **Estimated Effort**: broken down by phase (in hours)
-- **Questions & Clarifications**: seed 3-6 questions for the clarify phase — these become input for phase 4
-
-### Step 5: Register state
-
-```bash
-morph-spec state init {feature-name}
-morph-spec state set {feature-name} status draft
-morph-spec state mark-output {feature-name} proposal
-```
-
-### Step 6: Create pipeline master tasks
-
-> **MANDATORY** — Create one native task per pipeline phase for progress visibility.
-> These are high-level tasks — one per phase, not per workflow step.
-
-```
-TaskCreate: "Phase 0: Proposal"     → description: "Define feature scope and approach"          → activeForm: "Proposal"
-TaskCreate: "Phase 1: Setup"        → description: "Load context, detect agents, confirm stack"  → activeForm: "Setup"
-TaskCreate: "Phase 3: Design"       → description: "Schema analysis, spec, contracts, decisions" → activeForm: "Design"
-TaskCreate: "Phase 4: Clarify"      → description: "Resolve ambiguities and edge cases"          → activeForm: "Clarify"
-TaskCreate: "Phase 5: Plan"         → description: "Implementation plan with TDD and file paths" → activeForm: "Plan"
-TaskCreate: "Phase 6: Tasks"        → description: "Break spec into T001-T00N with dependencies" → activeForm: "Tasks"
-```
-
-If `ui-designer` is among the activated agents, also create:
-```
-TaskCreate: "Phase 2: UI/UX"       → description: "Design system, mockups, components, flows"   → activeForm: "UI/UX"
-```
-
-Wire dependencies (addBlockedBy) matching the phase sequence:
-- Setup ← Proposal
-- UI/UX (if created) ← Setup
-- Design ← UI/UX (or Setup if no UI/UX)
-- Clarify ← Design
-- Plan ← Clarify
-- Tasks ← Plan
-
-Mark "Phase 0: Proposal" as `in_progress` immediately.
-
-### MANDATORY PAUSE
-
-Use `AskUserQuestion` to present the approval gate with these elements:
-
-1. **Proposal summary** — 3-4 sentence overview of what was proposed
-2. **Agents activated** — table showing agent ID, tier, role, and why selected
-3. **Effort estimate** — total hours from the proposal
-4. **Key decisions pending** — 2-3 design decisions that will be resolved in the design phase
-
-Options: Approve proposal / Request changes / Reject
-
-After approval:
-```bash
-morph-spec approve {feature-name} proposal
-morph-spec phase advance {feature-name}
-```
-
----
-
-## 3. PHASE 1: SETUP (automatic, no pause)
-
-Invoke the `morph-phase-setup` skill.
-
-Summary: load project context, confirm stack, list active agents, update state.
-
-> **Task lifecycle:** `TaskUpdate` the "Phase 0: Proposal" task → `completed`. `TaskUpdate` the "Phase 1: Setup" task → `in_progress`.
-
-**No pause here.** Continue automatically to the next phase.
-
----
-
-## 4. PHASE 2: UI/UX (conditional)
-
-Check if `ui-designer` is in `activeAgents`:
-- **Yes:** Invoke the `morph-phase-uiux` skill. **MANDATORY PAUSE** after generating UI deliverables.
-- **No:** Skip to PHASE 3.
-
-> **Task lifecycle:** `TaskUpdate` the "Phase 1: Setup" task → `completed`. `TaskUpdate` the "Phase 2: UI/UX" task → `in_progress` (if UI/UX), or the "Phase 3: Design" task → `in_progress` (if skipping UI/UX).
-
-After approval:
-```bash
-morph-spec approve {feature-name} uiux
-morph-spec phase advance {feature-name}
-```
-
----
-
-## 5. PHASE 3: DESIGN
-
-> **Task lifecycle:** `TaskUpdate` the completing phase task (UI/UX or Setup) → `completed`. `TaskUpdate` the "Phase 3: Design" task → `in_progress`.
-
-Invoke the `morph-phase-design` skill.
-
-Summary: generate spec.md, contracts.cs (or contracts-vsa.cs for VSA), decisions.md with ADRs.
-
-### MANDATORY PAUSE
-
-Present: spec, contracts, decisions, effort estimate. Use `AskUserQuestion` with options: Approve design / Adjust scope / Modify contracts.
-
-After approval:
-```bash
-morph-spec approve {feature-name} design
-morph-spec phase advance {feature-name}
-```
-
----
-
-## 6. PHASE 4: CLARIFY (interactive)
-
-> **Task lifecycle:** `TaskUpdate` the "Phase 3: Design" task → `completed`. `TaskUpdate` the "Phase 4: Clarify" task → `in_progress`.
-
-Invoke the `morph-phase-clarify` skill.
-
-Summary: identify ambiguities in spec.md, generate 3-7 targeted questions (building on the questions seeded in the proposal), wait for user answers, update spec with clarifications and edge cases.
-
-**Wait for user responses before continuing.**
-
----
-
-## 7. PHASE 5: PLAN
-
-> **Task lifecycle:** `TaskUpdate` the "Phase 4: Clarify" task → `completed`. `TaskUpdate` the "Phase 5: Plan" task → `in_progress`.
-
-Invoke the `morph-phase-plan` skill.
-
-Summary: generate a detailed implementation plan with exact file paths, TDD structure, and context-aware execution strategy.
-
-### MANDATORY PAUSE
-
-Present: implementation plan with recommended strategy. Use `AskUserQuestion` with options: Approve plan / Adjust strategy / Modify plan.
-
-After approval:
-```bash
-morph-spec approve {feature-name} plan
-morph-spec phase advance {feature-name}
-```
-
----
-
-## 8. PHASE 6: TASKS
-
-> **Task lifecycle:** `TaskUpdate` the "Phase 5: Plan" task → `completed`. `TaskUpdate` the "Phase 6: Tasks" task → `in_progress`.
-
-Invoke the `morph-phase-tasks` skill.
-
-Summary: break spec into tasks T001-TXXX with dependencies, checkpoints, estimates.
-
-### MANDATORY PAUSE
-
-Present: task breakdown, execution order, total estimate. Use `AskUserQuestion` with options: Approve tasks / Reprioritize / Add or remove tasks.
-
-After approval:
-```bash
-morph-spec approve {feature-name} tasks
-morph-spec phase advance {feature-name}
-```
-
----
-
-## 9. Planning Complete
-
-> **Task lifecycle:** `TaskUpdate` the "Phase 6: Tasks" task → `completed`.
-
-After task approval:
-
-```
-Planning complete! Run /morph-apply {feature-name} to start implementation.
-```
-
----
-
-**Feature requested:** $ARGUMENTS
+---
+description: MORPH Spec Pipeline — creates or resumes feature planning through proposal, design, plan, and tasks phases with mandatory approval pauses. Use whenever the user wants to plan, spec, or design a new feature, or when they say /morph-proposal. This is the primary entry point for all MORPH-SPEC feature work.
+argument-hint: <feature-name>
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
+---
+
+# MORPH Spec Pipeline
+
+Guide a feature through the full planning pipeline (proposal through tasks) with mandatory approval pauses at each gate.
+
+---
+
+## 1. Resume Logic
+
+Check if the feature already has state:
+
+```bash
+morph-spec state get {feature-name}
+```
+
+- **Exists:** Read the current phase and resume from where it stopped (skip completed phases). Create pipeline master tasks (Step 6) and mark already-completed phases as `completed`.
+- **Does not exist:** Start from scratch (PHASE 0)
+
+---
+
+## 2. PHASE 0: PROPOSAL
+
+### Step 1: Load project context
+
+Read these files to understand the project before writing anything:
+- `.morph/context/README.md` — project overview, tech stack, architecture
+- `.morph/config/config.json` — project configuration (language, workflow, architecture style)
+
+### Step 2: Detect agents
+
+Read `framework/agents.json` (or `.morph/framework/agents.json` in client projects). For each agent:
+1. Check if `always_active: true` — include automatically
+2. Compare agent `keywords[]` and `domains[]` against the feature description — include on match
+3. **Document false-positive exclusions**: for agents that match on keywords but are irrelevant to this feature, note why they were excluded (this helps audit agent selection later)
+
+Register each selected agent:
+```bash
+morph-spec state add-agent {feature-name} {agent-id}
+```
+
+### Step 3: Determine if UI/UX phase is needed
+
+If `ui-designer` is among the selected agents, the feature will trigger the UI/UX phase later. Note this decision — it affects the pipeline path.
+
+### Step 4: Create proposal
+
+Read the proposal template at `framework/templates/docs/proposal.md` first, then create:
+
+```
+.morph/features/{feature-name}/
+  0-proposal/proposal.md
+```
+
+Fill every section of the template. In particular:
+- **Metadata table**: date, author, status, priority, stack
+- **Problem Statement**: use the What/Who/Impact structure from the template
+- **Proposed Solution**: technical approach, key features, user journey
+- **Success Metrics**: quantified current vs target values
+- **Scope**: explicit In Scope, Out of Scope, and Future Considerations
+- **Risks**: table with likelihood, impact, mitigation
+- **Dependencies**: checklist of prerequisites
+- **Estimated Effort**: broken down by phase (in hours)
+- **Questions & Open Points**: seed 3-6 questions to be resolved during the design phase
+
+### Step 5: Register state
+
+```bash
+morph-spec state init {feature-name}
+morph-spec state set {feature-name} status draft
+morph-spec state mark-output {feature-name} proposal
+```
+
+### Step 6: Create pipeline master tasks
+
+> **MANDATORY** — Create one native task per pipeline phase for progress visibility.
+> These are high-level tasks — one per phase, not per workflow step.
+
+```
+TaskCreate: "Proposal"     → description: "Define feature scope and approach"
+TaskCreate: "Design"       → description: "Schema analysis, spec, contracts, decisions"
+TaskCreate: "Plan"         → description: "Implementation plan with TDD and file paths"
+TaskCreate: "Tasks"        → description: "Break spec into T001-T00N with dependencies"
+```
+
+If `ui-designer` is among the activated agents, also create:
+```
+TaskCreate: "UI/UX"        → description: "Design system, mockups, components, flows"
+```
+
+Wire dependencies matching the phase sequence:
+- UI/UX (if created) ← Proposal
+- Design ← UI/UX (or Proposal if no UI/UX)
+- Plan ← Design
+- Tasks ← Plan
+
+Mark "Proposal" as `in_progress` immediately.
+
+### MANDATORY PAUSE
+
+Use `AskUserQuestion` to present the approval gate with these elements:
+
+1. **Proposal summary** — 3-4 sentence overview of what was proposed
+2. **Agents activated** — table showing agent ID, tier, role, and why selected
+3. **Effort estimate** — total hours from the proposal
+4. **Key decisions pending** — 2-3 design decisions that will be resolved in the design phase
+
+Options: Approve proposal / Request changes / Reject
+
+After approval:
+```bash
+morph-spec approve {feature-name} proposal
+morph-spec phase advance {feature-name}
+```
+
+---
+
+## 3. PHASE 1: UI/UX (conditional)
+
+Check if `ui-designer` is in `activeAgents`:
+- **Yes:** Invoke the `morph-phase-uiux` skill. **MANDATORY PAUSE** after generating UI deliverables.
+- **No:** Skip to PHASE 2.
+
+> **Task lifecycle:** `TaskUpdate` the "Proposal" task → `completed`. `TaskUpdate` the "UI/UX" task → `in_progress` (if UI/UX), or the "Design" task → `in_progress` (if skipping UI/UX).
+
+After approval:
+```bash
+morph-spec approve {feature-name} uiux
+morph-spec phase advance {feature-name}
+```
+
+---
+
+## 4. PHASE 2: DESIGN
+
+> **Task lifecycle:** `TaskUpdate` the completing phase task (UI/UX or Proposal) → `completed`. `TaskUpdate` the "Design" task → `in_progress`.
+
+Invoke the `morph-phase-design` skill.
+
+Summary: generate spec.md, contracts.cs (or contracts-vsa.cs for VSA), decisions.md with ADRs.
+
+### MANDATORY PAUSE
+
+Present: spec, contracts, decisions, effort estimate. Use `AskUserQuestion` with options: Approve design / Adjust scope / Modify contracts.
+
+After approval:
+```bash
+morph-spec approve {feature-name} design
+morph-spec phase advance {feature-name}
+```
+
+---
+
+## 5. PHASE 3: PLAN
+
+> **Task lifecycle:** `TaskUpdate` the "Design" task → `completed`. `TaskUpdate` the "Plan" task → `in_progress`.
+
+Invoke the `morph-phase-plan` skill.
+
+Summary: generate a detailed implementation plan with exact file paths, TDD structure, and context-aware execution strategy.
+
+### MANDATORY PAUSE
+
+Present: implementation plan with recommended strategy. Use `AskUserQuestion` with options: Approve plan / Adjust strategy / Modify plan.
+
+After approval:
+```bash
+morph-spec approve {feature-name} plan
+morph-spec phase advance {feature-name}
+```
+
+---
+
+## 6. PHASE 4: TASKS
+
+> **Task lifecycle:** `TaskUpdate` the "Plan" task → `completed`. `TaskUpdate` the "Tasks" task → `in_progress`.
+
+Invoke the `morph-phase-tasks` skill.
+
+Summary: break spec into tasks T001-TXXX with dependencies, checkpoints, estimates.
+
+### MANDATORY PAUSE
+
+Present: task breakdown, execution order, total estimate. Use `AskUserQuestion` with options: Approve tasks / Reprioritize / Add or remove tasks.
+
+After approval:
+```bash
+morph-spec approve {feature-name} tasks
+morph-spec phase advance {feature-name}
+```
+
+---
+
+## 7. Planning Complete
+
+> **Task lifecycle:** `TaskUpdate` the "Tasks" task → `completed`.
+
+After task approval:
+
+```
+Planning complete! Run /morph-apply {feature-name} to start implementation.
+```
+
+---
+
+**Feature requested:** $ARGUMENTS

package/framework/commands/morph-status.md

@@ -1,92 +1,72 @@
----
-description: Show current MORPH project status and all features in development with their phases and approvals
-argument-hint: [feature-name]
-allowed-tools: Read, Bash
----
-
-# MORPH Project Status
-
-Show the current MORPH project status and features in development.
-
-## Usage
-
-**ALWAYS** use the state-manager CLI to get status:
-
-```bash
-morph-spec state list
-```
-
-This command automatically shows:
-- All active features
-- Current phase of each feature
-- Task progress (X/Y)
-- Active agents
-- Estimated costs
-
-## Additional Checks
-
-### 1. MORPH Configuration
-- [ ] `.morph/project.md` exists and is filled in
-- [ ] `.morph/config/config.json` configured
-- [ ] `.morph/framework/standards/` present
-
-### 2. Specific Feature Details
-
-To get detailed JSON for a feature:
-
-```bash
-morph-spec state get {feature-name}
-```
-
-### 3. Archived Features
-
-Check `.morph/archive/` manually if needed:
-- How many features completed
-- Total time spent
-- Accumulated cost
-
-### 4. Active Specs
-
-Check `.morph/specs/` for consolidated specs.
-
-## Output
-
-The `morph-spec state list` command automatically generates a formatted dashboard:
-
-```
-╔════════════════════════════════════════════════════════════════╗
-║                    MORPH-SPEC PROJECT STATUS                   ║
-╠════════════════════════════════════════════════════════════════╣
-║ Project: {PROJECT_NAME}                                        ║
-║ Type: dotnet-nextjs                                            ║
-╠════════════════════════════════════════════════════════════════╣
-║ FEATURES                                                       ║
-╠════════════════════════════════════════════════════════════════╣
-║ 📝 {feature-1}                                                 ║
-║    Phase: implement        │ Tasks: 5/12                       ║
-║    Agents: ef-modeler hangfire-orchestrator                    ║
-╠════════════════════════════════════════════════════════════════╣
-║ 📝 {feature-2}                                                 ║
-║    Phase: design           │ Tasks: 0/0                        ║
-║    Agents: None                                                ║
-╠════════════════════════════════════════════════════════════════╣
-║ SUMMARY                                                        ║
-╠════════════════════════════════════════════════════════════════╣
-║ Total Features: 2                                              ║
-║ Completed: 0                                                   ║
-║ Estimated Cost: $5.50/month                                    ║
-╚════════════════════════════════════════════════════════════════╝
-```
-
-**Simply run the command and show the result to the user.**
-
-## Available Actions
-
-Suggest next actions:
-- `/morph-proposal {feature}` - Create a new feature
-- `/morph-apply {feature}` - Implement a feature
-- `/morph-archive {feature}` - Archive a completed feature
-
----
-
-$ARGUMENTS
+---
+description: Show current MORPH project status and all features in development with their phases and approvals
+argument-hint: [feature-name]
+allowed-tools: Read, Bash
+---
+
+# MORPH Project Status
+
+Show the current MORPH project status and features in development.
+
+## Usage
+
+**ALWAYS** use the state-manager CLI to get status:
+
+```bash
+morph-spec state list
+```
+
+This command automatically shows:
+- All active features
+- Current phase of each feature
+- Task progress (X/Y)
+- Active agents
+
+## Additional Checks
+
+### 1. MORPH Configuration
+- [ ] `.morph/config/config.json` configured
+- [ ] `.morph/framework/standards/` present
+
+### 2. Specific Feature Details
+
+To get detailed JSON for a feature:
+
+```bash
+morph-spec state get {feature-name}
+```
+
+## Output
+
+The `morph-spec state list` command automatically generates a formatted dashboard:
+
+```
+╔════════════════════════════════════════════════════════════════╗
+║                    MORPH-SPEC PROJECT STATUS                   ║
+╠════════════════════════════════════════════════════════════════╣
+║ Project: {PROJECT_NAME}                                        ║
+║ Type: dotnet-nextjs                                            ║
+╠════════════════════════════════════════════════════════════════╣
+║ FEATURES                                                       ║
+╠════════════════════════════════════════════════════════════════╣
+║  {feature-1}                                                   ║
+║    Phase: implement        | Tasks: 5/12                       ║
+║    Agents: ef-modeler hangfire-orchestrator                     ║
+╠════════════════════════════════════════════════════════════════╣
+║  {feature-2}                                                   ║
+║    Phase: design           | Tasks: 0/0                        ║
+║    Agents: None                                                ║
+╚════════════════════════════════════════════════════════════════╝
+```
+
+**Simply run the command and show the result to the user.**
+
+## Available Actions
+
+Suggest next actions:
+- `/morph-proposal {feature}` - Create a new feature
+- `/morph-apply {feature}` - Implement a feature
+
+---
+
+$ARGUMENTS