godpowers 2.1.1 → 2.2.1

package/schema/state.v1.json

@@ -74,6 +74,31 @@
       "description": "Slot for linkage map summary. Authoritative file is .godpowers/linkage.json.",
       "additionalProperties": true
     },
+    "deliverables": {
+      "type": "object",
+      "description": "Cached deliverable summary (requirement and roadmap-increment status). Recomputed fresh by lib/requirements.js from PRD + ROADMAP + linkage + build state; the human-readable ledger is .godpowers/REQUIREMENTS.md.",
+      "additionalProperties": true,
+      "properties": {
+        "updated": { "type": "string" },
+        "source": { "type": "string" },
+        "requirements": {
+          "type": "object",
+          "additionalProperties": true,
+          "properties": {
+            "total": { "type": "integer", "minimum": 0 },
+            "done": { "type": "integer", "minimum": 0 },
+            "in-progress": { "type": "integer", "minimum": 0 },
+            "untouched": { "type": "integer", "minimum": 0 },
+            "percent": { "type": "integer", "minimum": 0, "maximum": 100 }
+          }
+        },
+        "increments": {
+          "type": "array",
+          "items": { "type": "object", "additionalProperties": true }
+        },
+        "gaps": { "type": "integer", "minimum": 0 }
+      }
+    },
     "source-systems": {
       "type": "array",
       "description": "Detected external planning systems imported into Godpowers and eligible for managed sync-back.",

package/skills/god-doctor.md

@@ -48,9 +48,9 @@ Plain-text report grouped by severity:
 GODPOWERS DOCTOR
 
 Install: claude (~/.claude/)
-  [OK] 110 skills installed
+  [OK] 111 skills installed
   [OK] 40 agents installed
-  [OK] VERSION matches (2.1.1)
+  [OK] VERSION matches (2.2.1)
   [WARN] routing/god-doctor.yaml exists but skill file did not until now
 
 Project: /Users/.../my-project/.godpowers/

package/skills/god-locate.md

@@ -41,6 +41,7 @@ GODPOWERS LOCATE
 Project: <name>  Mode: <A/B/C/E>  Suite: <yes/no>
 Lifecycle: <phase>  Current: <tier>/<substep>
 Progress: <pct>% (<complete> of <total> steps complete; current step <n> of <total>)
+Deliverables: <done>/<total> requirements done (state.json cache; full list in .godpowers/REQUIREMENTS.md)
 
 Last action: <name> by <actor> at <ts>
 Last user instruction: <if available>

package/skills/god-progress.md

@@ -0,0 +1,105 @@
+---
+name: god-progress
+description: |
+  Deliverable progress report. Answers "what is done, what is in progress, and
+  what is left?" at the requirement and roadmap-increment level (not the
+  pipeline-stage level that /god-status leads with). Re-derives everything from
+  disk and refreshes the .godpowers/REQUIREMENTS.md ledger.
+
+  Triggers on: "god progress", "what's done", "what's left", "requirements
+  status", "how far along are we", "show me the checklist", "deliverable
+  progress", "what did we finish".
+---
+
+# God Progress
+
+Report deliverable progress: which requirements are done, in progress, or not
+started, and which roadmap increments are complete. This is the requirement-level
+companion to `/god-status` (which leads with pipeline-stage progress and
+proactive ops). Never report from memory; re-derive from disk every time.
+
+## Process
+
+1. If `.godpowers/state.json` is missing: say
+   "No Godpowers project found. Run `/god-init` to start." and stop.
+2. Resolve the runtime root and load `<runtimeRoot>/lib/requirements.js`.
+3. Call `requirements.derive(projectRoot)`. This reads, all from disk:
+   - `.godpowers/prd/PRD.md` for declared requirements (P-MUST/SHOULD/COULD ids)
+   - `.godpowers/roadmap/ROADMAP.md` for delivery increments and their members
+   - `.godpowers/links/` for the linkage forward map (requirement -> code)
+   - `.godpowers/state.json` for build and increment completion
+4. Refresh the ledger: `requirements.writeLedger(projectRoot, derived)` so
+   `.godpowers/REQUIREMENTS.md` always reflects current disk truth.
+5. Compute "what's next": the highest-priority requirement that is not yet done
+   (MUST before SHOULD before COULD), preferring one whose increment is already
+   building. Fall back to `router.suggestNext(projectRoot)` for the command.
+6. Render the report below.
+
+If `requirements.derive` reports `hasRequirements: false` (no PRD requirements
+declared yet), say so plainly and route the user to `/god-prd`, then stop.
+
+## Output Format
+
+```text
+Godpowers Progress
+
+Source: disk (PRD + ROADMAP + linkage + build state)
+Ledger: .godpowers/REQUIREMENTS.md
+
+Requirements: [########------------] 8/14 done (57%)
+  In progress: 3
+  Not started: 3
+  By priority:  MUST 6/8 | SHOULD 2/4 | COULD 0/2
+
+Increments:
+  [x] M-auth: Authentication [now] - done - 3/3 requirements
+  [~] M-billing: Billing [now] - building - 1/4 requirements
+  [ ] M-reports: Reporting [next] - pending - 0/3 requirements
+
+Recently done:
+  + P-MUST-05 Password reset emails send  (M-auth)
+  + P-MUST-06 Sessions expire after 24h   (M-auth)
+
+In progress now:
+  ~ P-MUST-07 Stripe webhook handling      (M-billing) - src/billing/webhook.ts
+
+Up next:
+  P-MUST-08 Invoice PDF generation (M-billing, not started)
+  Recommended command: /god-build
+  Why: M-billing is the current increment and P-MUST-08 is its next MUST.
+
+Gaps:
+  none
+  (or: P-MUST-09 is in a done increment but has no linked code)
+
+Open the full checklist any time: .godpowers/REQUIREMENTS.md
+```
+
+Use plain text. No emoji, no box-drawing. Ledger marks are `[x]` done, `[~]`
+in progress, `[ ]` not started, matching the ledger file.
+
+## Proposition Closeout
+
+End every progress report with a proposition block:
+
+```text
+Proposition:
+  1. Implement partial: [single next command, e.g. /god-build]
+  2. Implement complete: /god-mode to continue the project run when unblocked
+  3. Inspect deeper: open .godpowers/REQUIREMENTS.md or run /god-status
+  4. Discuss more: /god-discuss [a gap, a blocked requirement, or scope]
+Recommended: [one option and one sentence on why it fits the disk state]
+```
+
+If `derived.gaps` is non-empty, make `/god-review-changes` (or fixing the gap)
+the partial option and call the gap out first, since a done increment with
+unlinked code is a real inconsistency.
+
+## Relationship to other commands
+
+- `/god-status` - pipeline-stage progress (which tier/sub-step), proactive ops,
+  and overall readiness. Use when you want the operational picture.
+- `/god-progress` - deliverable progress (which requirements/increments).
+  Use when you want to know how much of the actual product is built.
+- `/god-next` - just the single recommended next command.
+- `.godpowers/REQUIREMENTS.md` - the static checklist file to open or share.

package/skills/god-status.md

@@ -33,6 +33,7 @@ Re-derive state from disk. Your memory is not authoritative. The file system is.
    - `.godpowers/harden/FINDINGS.md`
    - `.godpowers/SYNC-LOG.md`
    - `.godpowers/CHECKPOINT.md`
+   - `.godpowers/REQUIREMENTS.md`
 6. For each artifact found: run a lightweight have-nots check
 7. Compare disk state to PROGRESS.md state:
    - If PROGRESS.md says "done" but artifact is missing: FLAG as phantom resume
@@ -44,6 +45,9 @@ Re-derive state from disk. Your memory is not authoritative. The file system is.
    - Workflow progress summary: percentage, completed step count, current step number
    - Planning visibility: PRD status, roadmap status, active milestone, and
      completion basis
+   - Deliverable progress: requirement and increment status from
+     `lib/requirements` (requirements done / in progress / not started, by
+     priority, and increment counts), or "none declared yet" before a PRD exists
    - What happened recently, using CHECKPOINT.md actions when available
    - Last sync status, using SYNC-LOG.md when available
    - Proactive opportunities based on the auto-invoke policy
@@ -83,6 +87,12 @@ Planning visibility:
   Current milestone: Planning / Architecture
   Completion basis: .godpowers/state.json workflow steps
 
+Deliverable progress:
+  Requirements: [########------------] 8/14 done (57%), 3 in progress, 3 not started
+  By priority: MUST 6/8, SHOULD 2/4, COULD 0/2
+  Increments: 2 done, 1 building, 1 pending
+  Ledger: .godpowers/REQUIREMENTS.md
+
 What happened recently:
   1. PRD artifact verified on disk
   2. Tier state refreshed from state.json
@@ -137,6 +147,7 @@ Linkage status (from .godpowers/links/):
   Drift: 1 (colors.removed referenced in src/old.css but missing in DESIGN.md)
   Pending reviews: 5 (see REVIEW-REQUIRED.md)
   Last scan: 2026-05-10T14:23:11Z
+  Requirement checklist: run /god-progress or open .godpowers/REQUIREMENTS.md
 
 Suite (Mode D) status:
   This repo is a sibling of suite "my-products" (hub: ../hub)

package/skills/god-version.md

@@ -14,9 +14,9 @@ Print version and a short capability summary.
 ## Output
 
 ```
-Godpowers v2.1.1
+Godpowers v2.2.1
 Install: /Users/.../.claude/  (matches package.json)
-Surface: 110 skills, 40 agents, 13 workflows, 40 recipes
+Surface: 111 skills, 40 agents, 13 workflows, 41 recipes
 Schema: intent.v1, state.v1, events.v1, workflow.v1, routing.v1, recipe.v1
 External integrations available: impeccable, agent-browser (others lazy)
 Feature awareness: planning-system migration, source-system sync-back, context refresh, dashboard status labels, repo documentation sync, repo surface sync, quick proof, request trace, release hardening, maintenance hardening

package/templates/PRD.md

@@ -26,15 +26,22 @@
 
 ## Functional Requirements
 
+> Each requirement carries a stable id: `P-MUST-NN`, `P-SHOULD-NN`, `P-COULD-NN`.
+> These ids are load-bearing. The roadmap groups them into delivery increments,
+> code and tests reference them (`// Implements: P-MUST-01`,
+> `describe('P-MUST-01: ...')`), and `/god-progress` derives
+> done / in-progress / not-started status from them. Number sequentially within
+> each priority. Never renumber or reuse a shipped id.
+
 ### MUST (V1 launch blockers)
-- [DECISION] [Requirement] -- Acceptance: [observable criterion]
-- [DECISION] [Requirement] -- Acceptance: [observable criterion]
+- P-MUST-01 [DECISION] [Requirement] -- Acceptance: [observable criterion]
+- P-MUST-02 [DECISION] [Requirement] -- Acceptance: [observable criterion]
 
 ### SHOULD (V1 if time permits)
-- [HYPOTHESIS] [Requirement] -- Acceptance: [criterion] -- Validation: [how we'll test if this matters]
+- P-SHOULD-01 [HYPOTHESIS] [Requirement] -- Acceptance: [criterion] -- Validation: [how we'll test if this matters]
 
 ### COULD (post-V1)
-- [HYPOTHESIS] [Requirement]
+- P-COULD-01 [HYPOTHESIS] [Requirement]
 
 ## Non-Functional Requirements
 
@@ -75,6 +82,7 @@ Before declaring done, verify:
 - [ ] Problem statement fails substitution test
 - [ ] Target user is specific (not "developers")
 - [ ] Every success metric has a number AND timeline
+- [ ] Every functional requirement has a stable id (P-MUST-NN / P-SHOULD-NN / P-COULD-NN)
 - [ ] Every requirement has acceptance criteria
 - [ ] No-gos section is non-empty
 - [ ] Every open question has owner AND due date

package/templates/PROGRESS.md

@@ -8,6 +8,7 @@ Scale: [trivial | small | medium | large | enterprise]
 Started: [ISO 8601 timestamp]
 Last updated: [ISO 8601 timestamp]
 Progress: [0-100]% ([completed] of [total] steps complete; current step [n] of [total])
+Requirements: [done] of [total] done ([percent]%); [in-progress] in progress, [untouched] not started -- see .godpowers/REQUIREMENTS.md
 Current: [Tier N label] / [sub-step label]
 Host guarantees: [full | degraded | unknown]
 Action brief: [next command or user decision; readiness; top attention item]
@@ -41,6 +42,7 @@ Release readiness signals:
 - Dogfood status: [not-run | pass | fail | not applicable]
 - Repo documentation sync: [fresh | drift detected | not checked]
 - Repo surface sync: [fresh | drift detected | not checked]
+- Requirement coverage: [done]/[total] done; [gaps] gaps (see .godpowers/REQUIREMENTS.md)
 
 ## Tier Status
 

package/templates/REQUIREMENTS.md

@@ -0,0 +1,45 @@
+# Requirements Ledger
+
+> Disk-derived. Status comes from the linkage map (code that implements each
+> requirement) plus build and roadmap-increment state. Regenerate with
+> `/god-progress`, `/god-status`, or `/god-sync`. Do not hand-edit statuses;
+> they are recomputed from disk.
+>
+> This file is generated by `lib/requirements.js` (renderLedger). The block
+> below is an illustrative shape, not a file you fill in by hand.
+
+Updated: [ISO 8601 timestamp]
+Source: PRD + ROADMAP + linkage forward map + build state
+Progress: [########------------] 8/14 done (57%) | 3 in progress | 3 not started
+
+## By priority
+
+| Priority | Done | In progress | Not started | Total |
+|----------|------|-------------|-------------|-------|
+| MUST     | 6    | 1           | 1           | 8     |
+| SHOULD   | 2    | 1           | 1           | 4     |
+| COULD    | 0    | 1           | 1           | 2     |
+
+## Done (8)
+
+- [x] **P-MUST-01** User can sign in _(increment: M-auth)_ - src/auth/signin.ts, tests/auth/signin.test.ts
+
+## In progress (3)
+
+- [~] **P-MUST-07** Stripe webhook handling _(increment: M-billing)_ - src/billing/webhook.ts
+
+## Not started (3)
+
+- [ ] **P-MUST-08** Invoice PDF generation _(increment: M-billing)_
+
+## Increments
+
+- [x] **M-auth**: Authentication _[now]_ - done - 3/3 requirements done
+- [~] **M-billing**: Billing _[now]_ - building - 1/4 requirements done
+- [ ] **M-reports**: Reporting _[next]_ - pending - 0/3 requirements done
+
+## Gaps
+
+Requirements whose increment is marked done but have no implementing code linked:
+
+- (none)

package/templates/ROADMAP.md

@@ -2,32 +2,48 @@
 
 > Every delivery increment goal is substitution-tested. Every completion gate is
 > observable. No day-level precision without capacity input.
+>
+> Each increment carries a stable `**ID**: M-slug` and a `**Status**:` field, and
+> lists the PRD requirement ids it delivers under Features. `/god-progress` reads
+> these to show which increments are done, building, or pending, and to map each
+> requirement to its increment. Status is normally auto-derived from the linkage
+> map (code linked to the increment's requirements); set `**Status**: done`
+> explicitly only when the completion gate has been verified.
 
 ## Now (currently building, committed)
 
 ### Delivery Increment 1: [Substitution-tested goal]
+- **ID**: M-[slug]
+- **Status**: pending
 - **Goal**: [What users can DO when this ships. Specific.]
 - **Completion gate**: [Observable criterion. Not "feels done".]
 - **Size**: S / M / L
 - **Depends on**: None (or list)
 - **Features (from PRD)**:
-  - [PRD requirement reference]
-  - [PRD requirement reference]
+  - P-MUST-01
+  - P-MUST-02
 
 ### Delivery Increment 2: [Substitution-tested goal]
+- **ID**: M-[slug]
+- **Status**: pending
 - **Goal**: ...
 - **Completion gate**: ...
 - **Size**: S / M / L
-- **Depends on**: Delivery Increment 1
-- **Features**: ...
+- **Depends on**: M-[increment-1-slug]
+- **Features (from PRD)**:
+  - P-SHOULD-01
 
 ## Next (planned, flexible)
 
 ### Delivery Increment 3: [Goal]
+- **ID**: M-[slug]
+- **Status**: pending
 - **Goal**: ...
 - **Completion gate**: ...
 - **Size**: ...
-- **Depends on**: Delivery Increment 2
+- **Depends on**: M-[increment-2-slug]
+- **Features (from PRD)**:
+  - P-COULD-01
 
 ## Later (intent, not commitment)
 
@@ -39,6 +55,8 @@
 ## Have-Nots Checklist
 
 - [ ] Every delivery increment goal fails substitution test
+- [ ] Every increment has a stable M-slug id and a Status field
+- [ ] Every committed increment lists the PRD requirement ids (P-MUST-NN / ...) it delivers
 - [ ] Every completion gate is observable (not subjective)
 - [ ] No feature appears that isn't in the PRD
 - [ ] Delivery increments are NOT all the same size (real prioritization)