design-protocol 1.0.0

package/commands/dp-progress.md

@@ -0,0 +1,178 @@
+---
+name: dp-progress
+description: Display current DP workflow status, phase progress, and accumulated context. Shows where you are in the design process and what comes next.
+---
+
+# /dp:progress — View Workflow Status
+
+You are displaying the current DP workflow status. This command reads state and provides a clear picture of progress.
+
+## Workflow
+
+### Step 1: Check for Workflow
+
+Check if DP workflow exists:
+
+```bash
+ls .design/config.json 2>/dev/null
+```
+
+**If not found:**
+```
+No DP workflow found in this directory.
+
+Start one with: /dp:start
+Or run skills standalone: /dp:discovery, /dp:ux, /dp:ui, /dp:eng_review
+```
+
+### Step 2: Load and Validate State Files
+
+Read these files:
+- `.design/config.json` — Settings and workflow metadata
+- `.design/STATE.md` — Current position and context
+- `.design/PROJECT.md` — Project overview
+
+**Validate config.json** after reading:
+
+Required fields — if any are missing, warn the user and offer to repair:
+- `version` — must be a string (e.g., `"2.1"`)
+- `workflow.current_phase` — must be a number 0-4
+- `workflow.phases_completed` — must be an array
+- `workflow.workflow_status` — must be one of: `not_started`, `in_progress`, `blocked`, `complete`, `gaps`
+- `phases` — must be an object with `discovery`, `ux`, `ui`, `review` keys
+
+If JSON parsing fails entirely:
+```
+⚠ .design/config.json is corrupted or not valid JSON.
+
+Options:
+1. Rebuild from phase files (I'll scan .design/phases/ for completed work)
+2. Reset to defaults (keeps your phase output files intact)
+```
+
+If fields are missing but JSON is valid:
+```
+⚠ config.json is missing required fields: {list}
+  Adding defaults for missing fields...
+```
+Then fill in the missing fields with defaults from the config template and write the repaired file.
+
+**Cross-validate state consistency:**
+- If `phases_completed` includes a phase but the output file is missing, flag it:
+  `⚠ Phase "ux" marked complete but UX-DECISIONS.md not found`
+- If a phase output file exists but the phase isn't in `phases_completed`, flag it:
+  `⚠ DISCOVERY.md exists but discovery not marked complete — marking it now`
+
+### Step 3: Calculate Progress
+
+Determine completion percentage:
+- Phase 0 (not started): 0%
+- Phase 1 (discovery) complete: 25%
+- Phase 2 (ux) complete: 50%
+- Phase 3 (ui) complete: 75%
+- Phase 4 (review) complete: 100%
+
+Generate progress bar:
+- 0%: `[░░░░░░░░░░]`
+- 25%: `[██░░░░░░░░]`
+- 50%: `[█████░░░░░]`
+- 75%: `[███████░░░]`
+- 100%: `[██████████]`
+
+### Step 4: Display Status
+
+Output this format:
+
+```
+═══════════════════════════════════════════════════════════════════════════════
+DP WORKFLOW STATUS: [Project Name]
+═══════════════════════════════════════════════════════════════════════════════
+
+Progress: [██░░░░░░░░] 25%
+
+PHASE STATUS
+────────────────────────────────────────────────────────────────────────────────
+│ # │ Phase     │ Status    │ Completed  │ Output            │
+│───│───────────│───────────│────────────│───────────────────│
+│ 1 │ Discovery │ ● complete│ 2024-01-15 │ DISCOVERY.md      │
+│ 2 │ UX        │ ◐ current │ —          │ UX-DECISIONS.md   │
+│ 3 │ UI        │ ○ pending │ —          │ UI-SPEC.md        │
+│ 4 │ Review    │ ○ pending │ —          │ REVIEW.md         │
+
+Optional: Research — not enabled
+
+CURRENT POSITION
+────────────────────────────────────────────────────────────────────────────────
+Phase: 2 of 4 (UX)
+Status: In Progress
+Last Activity: [timestamp] — Completed discovery phase
+
+CONTEXT SUMMARY
+────────────────────────────────────────────────────────────────────────────────
+Problem: [One-liner from discovery]
+User: [Primary user role]
+Key Requirement: [Most important must-have]
+
+RECENT DECISIONS
+────────────────────────────────────────────────────────────────────────────────
+• Discovery: [Key decision 1]
+• Discovery: [Key decision 2]
+
+NEXT ACTIONS
+────────────────────────────────────────────────────────────────────────────────
+→ Run /dp:ux to continue with usability principles
+  Or /dp:discuss to capture decisions first
+
+═══════════════════════════════════════════════════════════════════════════════
+QUICK COMMANDS
+═══════════════════════════════════════════════════════════════════════════════
+/dp:discovery     — Discovery (Phase 1)      /dp:discuss  — Capture decisions
+/dp:ux           — UX principles (Phase 2)  /dp:skip     — Skip current phase
+/dp:ui           — Visual design (Phase 3)  /dp:back     — Go to previous phase
+/dp:eng_review — Review (Phase 4)      /dp:verify   — Check deliverables
+═══════════════════════════════════════════════════════════════════════════════
+```
+
+### Step 5: Show Phase Details (Optional)
+
+If user asks for more detail on a specific phase, read the corresponding file:
+- Discovery: `.design/phases/DISCOVERY.md`
+- UX: `.design/phases/UX-DECISIONS.md`
+- UI: `.design/phases/UI-SPEC.md`
+- Review: `.design/phases/REVIEW.md`
+
+Display a summary of that phase's output.
+
+## Status Icons
+
+- `●` complete — Phase finished
+- `◐` current — Currently active phase
+- `○` pending — Not yet started
+- `⊘` skipped — Explicitly skipped
+- `✕` blocked — Cannot proceed
+
+## Workflow Status Values
+
+From `config.json`:
+- `not_started` — Project initialized but no phase started
+- `in_progress` — Actively working through phases
+- `blocked` — Cannot proceed (show blockers from STATE.md)
+- `complete` — All phases done
+- `gaps` — Review found issues needing iteration
+
+## Error Handling
+
+- If STATE.md is corrupted, offer to rebuild from phase files
+- If phase files are missing but marked complete, flag inconsistency
+- Always show what commands are available regardless of state
+
+---
+
+## Workflow Navigation
+
+| | |
+|---|---|
+| **This command** | `/dp:progress` — View workflow status |
+| **Useful anytime** | Works at any point in the workflow |
+| **Related** | `/dp:start` — Initialize if no workflow found |
+| | `/dp:verify` — Detailed quality check at end of workflow |

package/commands/dp-roadmap.md

@@ -0,0 +1,83 @@
+---
+name: dp-roadmap
+description: Build a theme-based UX roadmap using NNGroup's Now/Next/Future methodology. Optional Phase 1.5c in DP workflow, between Discovery and UX.
+---
+
+# /dp:roadmap — UX Roadmap Phase
+
+You are running the UX roadmapping phase of the DP workflow. Invoke the `dp-roadmap` skill immediately.
+
+## What this command does
+
+Produces a strategic, living roadmap artifact using Sarah Gibbons' (NNGroup) methodology:
+- Theme-based, not feature-based
+- Now / Next / Future time horizons (default), or outcome-based / theme-ranked / lean variants
+- Every theme includes Beneficiary, Need, Business Objective, Confidence, Disclaimers
+- Integrates prioritization (RICE, ICE, MoSCoW, Kano, Value/Effort, or Opportunity Scoring)
+
+## Workflow
+
+### Step 1 — Detect workflow mode
+
+```bash
+ls .design/config.json 2>/dev/null
+```
+
+If found → workflow mode. Load:
+- `.design/config.json`
+- `.design/phases/DISCOVERY.md`
+- `.design/phases/JOURNEY-MAP.md` (if exists)
+- Any research artifacts under `.design/research/` (e.g., `RESEARCH-PLAN.md`, `FINDINGS-*.md`)
+- `.design/phases/PRD.md` (if exists)
+- `.design/phases/01.5c-CONTEXT.md` (if `/dp:discuss` was run)
+
+If not found → standalone mode. Ask scope (team / product / portfolio) and whether new vs. updating.
+
+### Step 2 — Invoke the skill
+
+Invoke the `dp-roadmap` skill. The skill drives:
+- Roadmap type selection (4 options)
+- High-level goals and scope definition
+- 6-step process: Goals → Inputs → Themes → Prioritize → Visualize → Revisit
+- Prioritization framework selection
+- Output generation
+
+### Step 3 — Write output
+
+**Workflow mode:** writes `.design/phases/ROADMAP.md` and updates STATE.md, config.json.
+
+**Standalone mode:** outputs inline; offers to save.
+
+### Step 4 — Handoff
+
+After completion, suggest next step:
+- `/dp:ux` — continue to UX phase (work on Now themes)
+- `/dp:prd` — generate PRD for highest-priority theme
+- `/dp:research` — validate low-confidence Future themes
+
+## When to use this command
+
+- Quarterly / annual UX planning at team or org level
+- Aligning stakeholders around a problem portfolio
+- Converting journey-map opportunities into prioritized work
+- Replacing a feature-based roadmap with a theme-based one
+- Re-planning after a strategic shift
+
+## When NOT to use this command
+
+- Sprint planning or backlog — too tactical, use a PM tool
+- Feature specs — use `/dp:prd`
+- Individual feature design — use `/dp:ux` + `/dp:ui`
+- Engineering/tech-debt roadmaps — different audience and criteria
+
+## Workflow Navigation
+
+| | |
+|---|---|
+| **Previous** | `/dp:discovery` — Discovery (Phase 1) |
+| **Parallel** | `/dp:prd` (1.5a), `/dp:journey` (1.5b) |
+| **This** | `/dp:roadmap` — Roadmap (Phase 1.5c) |
+| **Next** | `/dp:ux` — UX phase (Phase 2) |
+| **Related** | `/dp:research` — Close open questions |
+| | `/dp:discuss` — Capture context first |
+| | `/dp:back` — Return to discovery |

package/commands/dp-skip.md

@@ -0,0 +1,186 @@
+---
+name: dp-skip
+description: Skip the current DP workflow phase and move to the next one. Use when a phase is not needed or already addressed elsewhere.
+---
+
+# /dp:skip — Skip Current Phase
+
+You are skipping the current phase in the DP workflow. This moves to the next phase without running the current phase's skill.
+
+## When to Use
+
+- Phase requirements already met elsewhere
+- Time constraints require skipping
+- Phase not applicable for this project
+- User wants to focus on specific phases only
+
+## Workflow
+
+### Step 1: Check Workflow Exists
+
+```bash
+ls .design/config.json 2>/dev/null
+```
+
+### Step 2: Get Current Phase
+
+Read `.design/STATE.md` and `.design/config.json` to determine:
+- Current phase number
+- Current phase name
+- Next phase
+
+### Step 3: Confirm Skip
+
+Ask for confirmation:
+
+```
+You're about to skip: Phase [N] — [Phase Name]
+
+This phase would normally produce: [output file]
+
+Skipping means:
+• No [output] will be generated
+• Next phase won't have this context
+• /dp:verify may flag missing artifacts
+
+Are you sure? (y/n)
+
+If you want to provide minimal context instead, use /dp:discuss first.
+```
+
+### Step 4: Handle Skip Options
+
+**If confirmed:**
+1. Update `.design/STATE.md`:
+   - Mark current phase as "skipped"
+   - Set next phase as current
+   - Add skip to activity log
+   - Note reason if provided
+
+2. Update `.design/config.json`:
+   - Add current phase to `phases_completed` with status "skipped"
+   - Increment `current_phase`
+
+3. Create placeholder in `.design/phases/`:
+   - Create `{PHASE_NAME}.md` with skip marker
+   ```markdown
+   # [Phase Name]: SKIPPED
+
+   > Skipped: [TIMESTAMP]
+   > Reason: [user provided reason or "User chose to skip"]
+
+   This phase was skipped. Context may be incomplete for subsequent phases.
+
+   To complete this phase later, run: /[skill-name]
+   ```
+
+**Output:**
+```
+✓ Skipped: Phase [N] — [Phase Name]
+
+New Position:
+  Phase: [N+1] of 4 ([Next Phase Name])
+  Status: Ready
+  Progress: [████░░░░░░] [X]%
+
+Next: Run /[next-skill] to continue
+      Or /dp:back to return to [Phase Name]
+```
+
+### Step 5: Edge Cases
+
+**Skipping Discovery (Phase 1):**
+```
+⚠️ Skipping Discovery is not recommended.
+
+Discovery establishes:
+• Problem statement
+• User personas
+• Requirements
+• Constraints
+
+Without discovery, subsequent phases lack critical context.
+
+Alternatives:
+1. /dp:discuss — Provide minimal context without full interrogation
+2. Paste existing brief — If you have a design brief, share it and I'll extract context
+
+Still skip? (y/n)
+```
+
+**Skipping Review (Phase 4):**
+```
+Skipping Review means:
+• No quality score
+• No accessibility audit
+• No spec alignment check
+
+This is only recommended if:
+• Code hasn't been implemented yet
+• You'll run /dp:eng_review later
+
+Skip anyway? (y/n)
+```
+
+**Skipping when already on last phase:**
+```
+You're on the last phase (Review).
+
+Options:
+• Run /dp:eng_review to complete the workflow
+• Run /dp:verify to check deliverables
+• Consider the workflow complete without formal review
+```
+
+**All phases skipped:**
+If user tries to skip all phases, warn that this defeats the purpose:
+```
+⚠️ All phases would be skipped.
+
+If you don't need the DP workflow, run skills standalone instead:
+• /dp:discovery — Discovery
+• /dp:ux — Usability
+• /dp:ui — Visual design
+• /dp:eng_review — Code review
+
+These work without the workflow infrastructure.
+```
+
+## State Updates
+
+**STATE.md updates:**
+```markdown
+## Phase Status
+
+| # | Phase | Status | Completed | Output |
+|---|-------|--------|-----------|--------|
+| 1 | Discovery | ⊘ skipped | 2024-01-15 | — |
+| 2 | UX | ◐ current | — | UX-DECISIONS.md |
+```
+
+**Activity log entry:**
+```markdown
+### Last Activity
+- **Date:** [TIMESTAMP]
+- **Action:** Skipped Discovery phase
+- **Reason:** [User provided reason]
+```
+
+## Recovery
+
+To undo a skip:
+1. `/dp:back` returns to the skipped phase
+2. Running the phase skill will generate the output
+3. Phase status changes from "skipped" to "completed"
+
+---
+
+## Workflow Navigation
+
+| | |
+|---|---|
+| **This command** | `/dp:skip` — Skip current phase |
+| **Use when** | Phase output already exists or isn't needed |
+| **Advances to** | The next phase in sequence |
+| **Undo with** | `/dp:back` — Return to the skipped phase |
+| **Related** | `/dp:progress` — See current phase and what was skipped |