Skip to content

Commit 04de226

Browse files
davidleedavidlee
committed
doc(DE-083)
1 parent abcdc8c commit 04de226

4 files changed

Lines changed: 189 additions & 18 deletions

File tree

‎.spec-driver/deltas/DE-083-strengthen_audit_to_spec_reconciliation_and_spec_revision_authorship_skills/DE-083.md‎

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,8 @@ requirements:
4040
implements: []
4141
updates: []
4242
verifies: []
43-
phases: []
43+
phases:
44+
- IP-083.PHASE-01
4445
```
4546
4647
## 1. Summary & Context
@@ -49,7 +50,7 @@ phases: []
4950
- `PROD-002` - delta bundle expectations and handoff surfaces for follow-up design/planning work
5051
- **Technical Spec(s)**:
5152
- `SPEC-151` - skills library implementation surface; still too thin for the remaining authorship-skill work
52-
- **Implementation Plan**: [IP-083](./IP-083.md) - scaffolded; phase planning intentionally deferred until `DR-083` is shaped
53+
- **Implementation Plan**: [IP-083](./IP-083.md) - phase planning now starts at executable work because `DR-083` has already settled the design boundary
5354
- **Change Drivers**:
5455
- `DE-055` closure handoff: routing and DR-loop guidance landed, but deeper audit-to-spec and authorship-skill work was intentionally split out
5556
- `DE-079` runtime audit reconciliation contract: introduces the machine-checkable audit flow that authorship skills must feed cleanly

‎.spec-driver/deltas/DE-083-strengthen_audit_to_spec_reconciliation_and_spec_revision_authorship_skills/IP-083.md‎

Lines changed: 12 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -28,14 +28,10 @@ requirements:
2828
dependencies: []
2929
phases:
3030
- id: IP-083.PHASE-01
31-
name: Shape audit-to-spec authorship design
32-
objective: Settle the authorship-skill boundary and the preferred reconciliation path from audit findings into specs.
31+
name: Apply revision/spec authorship changes
32+
objective: Update the affected skills and direct governance surfaces to implement the settled audit-to-spec authorship path.
3333
status: planned
3434
- id: IP-083.PHASE-02
35-
name: Apply revision/spec authorship skill changes
36-
objective: Update the chosen skill surfaces so the authorship path is concrete and doctrine-aware.
37-
status: planned
38-
- id: IP-083.PHASE-03
3935
name: Verify audit-to-spec examples and reconcile docs
4036
objective: Prove the designed path with worked examples and keep DE/DR/IP/notes aligned.
4137
status: planned
@@ -82,22 +78,22 @@ entries:
8278
## 4. Phase Overview
8379
| Phase | Objective | Entrance Criteria | Exit Criteria / Done When | Phase Sheet |
8480
| --- | --- | --- | --- | --- |
85-
| Phase 0 - Shape audit-to-spec authorship design | Decide the authorship boundary and the preferred reconciliation path | Delta scoped; `DE-055` and `DE-079` boundaries understood | `DR-083` answers the major branch questions and phase 1 is implementable | `phases/phase-01.md` |
86-
| Phase 1 - Apply authorship skill changes | Update the chosen skill surfaces | Phase 0 complete; touched skills identified | Skill wording and any spec/revision docs reflect the chosen authorship path | `phases/phase-02.md` |
87-
| Phase 2 - Verify worked examples and reconcile docs | Validate the new path and update delta docs | Phase 1 complete; examples selected | Worked examples, notes, and DE/DR/IP artefacts agree on the final authorship path | `phases/phase-03.md` |
81+
| Phase 1 - Apply authorship skill changes | Update the chosen skill surfaces and direct governance docs | `DR-083` resolved; touched surfaces identified; `DE-079` boundary understood | Skill wording and direct spec revisions reflect the chosen authorship path | `phases/phase-01.md` |
82+
| Phase 2 - Verify worked examples and reconcile docs | Validate the new path and update delta docs | Phase 1 complete; examples selected | Worked examples, notes, and DE/DR/IP artefacts agree on the final authorship path | `phases/phase-02.md` |
8883

89-
Phase sheets are intentionally deferred until `DR-083` is shaped; this plan records the expected execution shape, not implementation readiness.
84+
Design shaping is complete; execution planning now starts at phase 1.
9085

9186
## 5. Phase Detail Snapshot
9287
- **Research Notes**: `notes.md`
9388
- **Design Revision**: [DR-083](./DR-083.md)
94-
- **Active Phase Sheet**: none yet; create `phase-01.md` only after `DR-083` is current enough to drive execution
95-
- **Parallelisable Work**: low until the authorship-skill boundary is settled
96-
- **Plan Updates**: refine phase objectives after the major open questions in `DR-083` are resolved
97-
- `DR-083` now resolves the boundary: strengthen `audit-change` and `shape-revision`, keep new-spec creation revision-led, and treat `PROD-011` plus `SPEC-151` as direct revision targets
89+
- **Active Phase Sheet**: `phases/phase-01.md`
90+
- **Parallelisable Work**: limited; `audit-change` and `shape-revision` can partly advance in parallel once the direct spec revisions are scoped
91+
- **Plan Updates**:
92+
- design shaping is complete and now lives in `DR-083`, so execution planning begins at phase 1 rather than creating a retrospective design phase sheet
93+
- phase 1 owns `audit-change`, `shape-revision`, `PROD-011`, and `SPEC-151`, with `PROD-001`/`PROD-002` only if implementation confirms they need direct edits
9894

9995
## 6. Testing & Verification Plan
100-
- **Updated Suites**: to be decided after phase 0 identifies the concrete touched skill/code surfaces
96+
- **Updated Suites**: primarily document/skill review plus any skill-sync or command checks needed by the touched surfaces
10197
- **New Cases**: worked examples covering existing-spec patch, revision, and justified new-spec creation
10298
- **Tooling/Fixtures**: likely mostly document/skill review plus any tests added by follow-on implementation work
10399
- **Rollback Plan**: revert authorship-skill wording changes independently of `DE-079` runtime contract work
@@ -116,7 +112,7 @@ Phase sheets are intentionally deferred until `DR-083` is shaped; this plan reco
116112
- [x] Decide which specs or revisions must change once the skills are updated
117113

118114
## 9. Progress Tracking
119-
- [ ] Phase 0 complete
115+
- [x] Design shaping complete
120116
- [ ] Phase 1 complete
121117
- [ ] Phase 2 complete
122118
- [ ] Verification gates passed

‎.spec-driver/deltas/DE-083-strengthen_audit_to_spec_reconciliation_and_spec_revision_authorship_skills/notes.md‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,3 +24,10 @@
2424
- Resolved the main design boundary in `DR-083`: DE-083 should strengthen existing skills rather than introduce a dedicated spec-authoring skill.
2525
- Settled the branch order as `existing spec patch -> revision -> revision-led new spec`, keeping the new-spec case inside the existing `revision` audit disposition rather than reopening the `DE-079` contract.
2626
- Identified direct governance/spec revision targets as `PROD-011` and `SPEC-151`, with `PROD-002` and `PROD-001` treated as collaborator surfaces to confirm during implementation.
27+
28+
### Phase planning update
29+
- Created `IP-083.PHASE-01` via `uv run spec-driver create phase "Shape audit-to-spec authorship design" --plan IP-083`, then re-scoped it to the first executable phase now that design shaping is already complete.
30+
- Collapsed the remaining execution plan to two phases:
31+
- phase 1 applies the skill and direct governance changes
32+
- phase 2 verifies worked examples and reconciles the delta docs
33+
- Added concrete entrance/exit criteria, verification expectations, STOP conditions, and task breakdown for phase 1.

‎.spec-driver/deltas/DE-083-strengthen_audit_to_spec_reconciliation_and_spec_revision_authorship_skills/phases/phase-01.md‎

Lines changed: 167 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,167 @@
1+
---
2+
id: IP-083.PHASE-01
3+
slug: 083-strengthen_audit_to_spec_reconciliation_and_spec_revision_authorship_skills-phase-01
4+
name: "IP-083 Phase 01 — Apply authorship skill changes"
5+
created: '2026-03-09'
6+
updated: '2026-03-09'
7+
status: draft
8+
kind: phase
9+
---
10+
11+
```yaml supekku:phase.overview@v1
12+
schema: supekku.phase.overview
13+
version: 1
14+
phase: IP-083.PHASE-01
15+
plan: IP-083
16+
delta: DE-083
17+
objective: >-
18+
Update the affected skills and direct governance surfaces so the settled
19+
audit-to-spec authorship path is executable without reopening design.
20+
entrance_criteria:
21+
- DR-083 resolves the dedicated-skill question and the branch criteria
22+
- DE-079 boundary is accepted: no schema or gating changes in this phase
23+
- Direct revision targets are identified as PROD-011 and SPEC-151
24+
exit_criteria:
25+
- audit-change teaches existing-spec patch -> revision -> revision-led new spec
26+
- shape-revision teaches post-audit triage, doctrine pass, and section-by-section authorship
27+
- PROD-011 reflects the canonical audit-to-spec reconciliation path and concession posture
28+
- SPEC-151 states the strengthened skills subsystem responsibilities
29+
- Need for PROD-001 or PROD-002 edits is resolved and any required edits are applied
30+
- Installed skill copies and delta docs are reconciled after the packaged changes
31+
verification:
32+
tests:
33+
- uv run spec-driver skills sync
34+
- uv run spec-driver show delta DE-083
35+
evidence:
36+
- Updated packaged and installed skill wording for audit-change and shape-revision
37+
- Revised PROD-011 and SPEC-151 text aligned with DR-083
38+
- Notes capturing whether PROD-001 and PROD-002 required direct changes
39+
tasks:
40+
- id: "1.1"
41+
title: Update audit-change with explicit authorship ordering
42+
status: todo
43+
- id: "1.2"
44+
title: Upgrade shape-revision into the post-audit authorship loop
45+
status: todo
46+
- id: "1.3"
47+
title: Reassess spec-driver wording for the revision-led create-spec branch
48+
status: todo
49+
- id: "1.4"
50+
title: Revise PROD-011 for canonical audit-to-spec reconciliation
51+
status: todo
52+
- id: "1.5"
53+
title: Replace the SPEC-151 stub boundary with explicit responsibilities
54+
status: todo
55+
- id: "1.6"
56+
title: Patch PROD-001 or PROD-002 only if implementation proves a direct wording gap
57+
status: todo
58+
- id: "1.7"
59+
title: Sync installed skills and reconcile DE/IP/notes
60+
status: todo
61+
risks:
62+
- description: New-spec wording could drift into a peer audit disposition and conflict with DE-079
63+
mitigation: Keep the new-spec case nested under revision in every touched surface
64+
- description: Direct spec revisions could sprawl into collaborator surfaces without clear need
65+
mitigation: Treat PROD-001 and PROD-002 as opt-in edits gated by explicit wording gaps
66+
```
67+
68+
```yaml supekku:phase.tracking@v1
69+
schema: supekku.phase.tracking
70+
version: 1
71+
phase: IP-083.PHASE-01
72+
```
73+
74+
# Phase 1 - Apply authorship skill changes
75+
76+
## 1. Objective
77+
Update the skills and direct governance surfaces identified by DR-083 so the
78+
post-audit authorship path is concrete enough to execute without re-opening the
79+
design questions.
80+
81+
## 2. Links & References
82+
- **Delta**: DE-083
83+
- **Design Revision Sections**:
84+
- Foundational Triage
85+
- Architecture Intent / Branch Criteria
86+
- Code Impact Summary
87+
- Readiness Outcome
88+
- **Specs / PRODs**:
89+
- `PROD-011`
90+
- `SPEC-151`
91+
- `PROD-001` (collaborator surface; edit only if needed)
92+
- `PROD-002` (collaborator surface; edit only if needed)
93+
- **Support Docs**:
94+
- `supekku/skills/audit-change/SKILL.md`
95+
- `supekku/skills/shape-revision/SKILL.md`
96+
- `supekku/skills/spec-driver/SKILL.md`
97+
- `.spec-driver/deltas/DE-055-tighten_skill_routing_and_boot_time_workflow_guidance/DR-055.md`
98+
- `.spec-driver/deltas/DE-079-implement_canonical_audit_reconciliation_contract/DR-079.md`
99+
100+
## 3. Entrance Criteria
101+
- [x] DR-083 resolves the dedicated-skill question and branch criteria
102+
- [x] Direct vs collaborator governance surfaces are identified
103+
- [x] DE-079 ownership boundary is clear and excludes runtime/schema changes from this phase
104+
105+
## 4. Exit Criteria / Done When
106+
- [ ] `audit-change` teaches `spec_patch -> revision -> revision-led new spec`
107+
- [ ] `shape-revision` teaches post-audit triage, doctrine consultation, and section-by-section authorship
108+
- [ ] `PROD-011` reflects the canonical audit-to-spec reconciliation path
109+
- [ ] `SPEC-151` captures the strengthened skills subsystem responsibilities
110+
- [ ] Need for `PROD-001` or `PROD-002` edits is resolved, with any required edits applied
111+
- [ ] Packaged and installed skill copies are synchronized and DE/IP/notes reflect the work
112+
113+
## 5. Verification
114+
- Tests to run:
115+
- `uv run spec-driver skills sync`
116+
- `uv run spec-driver show delta DE-083`
117+
- Tooling/commands:
118+
- `sed -n '1,260p' supekku/skills/audit-change/SKILL.md`
119+
- `sed -n '1,260p' supekku/skills/shape-revision/SKILL.md`
120+
- `sed -n '1,260p' .spec-driver/product/PROD-011/PROD-011.md`
121+
- `sed -n '1,200p' .spec-driver/tech/SPEC-151/SPEC-151.md`
122+
- Evidence to capture:
123+
- packaged and installed skill wording matches the DR-083 branch criteria
124+
- direct governance surfaces match the settled authorship boundary
125+
- notes record whether collaborator surfaces stayed untouched or required edits
126+
127+
## 6. Assumptions & STOP Conditions
128+
- Assumptions:
129+
- `spec-driver create spec` remains sufficient for the rare revision-led new-spec branch
130+
- no new audit disposition kind is required beyond `spec_patch` and `revision`
131+
- STOP when:
132+
- implementation reveals a need to change DE-079 audit schema, validation, or gate behaviour
133+
- a dedicated spec-authoring skill becomes necessary to express the design cleanly
134+
- required governance edits expand beyond `PROD-011`, `SPEC-151`, `PROD-001`, and `PROD-002`
135+
136+
## 7. Tasks & Progress
137+
*(Status: `[ ]` todo, `[WIP]`, `[x]` done, `[blocked]`)*
138+
139+
| Status | ID | Description | Parallel? | Notes |
140+
| --- | --- | --- | --- | --- |
141+
| [ ] | 1.1 | Update `audit-change` with explicit authorship ordering | [ ] | Closure-grade skill surface |
142+
| [ ] | 1.2 | Upgrade `shape-revision` into the post-audit authorship loop | [ ] | Reuse DR authoring patterns where justified |
143+
| [ ] | 1.3 | Reassess `spec-driver` wording for revision-led `create spec` | [P] | Only if current wording leaves a real gap |
144+
| [ ] | 1.4 | Revise `PROD-011` for canonical audit-to-spec reconciliation | [ ] | Direct governance target |
145+
| [ ] | 1.5 | Replace the `SPEC-151` stub boundary with explicit responsibilities | [ ] | Direct technical target |
146+
| [ ] | 1.6 | Patch `PROD-001` or `PROD-002` only if needed | [P] | Collaborator surfaces, not defaults |
147+
| [ ] | 1.7 | Sync installed skills and reconcile DE/IP/notes | [ ] | Finish with aligned artefacts |
148+
149+
## 8. Risks & Mitigations
150+
| Risk | Mitigation | Status |
151+
| --- | --- | --- |
152+
| New-spec wording drifts into a peer audit disposition | keep every touched surface aligned with `revision -> optional new spec` | active |
153+
| Collaborator-surface edits sprawl | require an explicit wording gap before touching `PROD-001` or `PROD-002` | active |
154+
| Packaged and installed skill copies diverge | run `uv run spec-driver skills sync` before phase close-out | active |
155+
156+
## 9. Decisions & Outcomes
157+
- `2026-03-09` - Phase planning starts at execution, not retrospective design capture. Rationale: DR-083 already settled the design questions before the first phase sheet was created.
158+
159+
## 10. Findings / Research Notes
160+
- DR-083 settled the branch order as existing-spec patch -> revision -> revision-led new spec.
161+
- Direct revision targets are `PROD-011` and `SPEC-151`; `PROD-001` and `PROD-002` are collaborator surfaces to justify before touching.
162+
163+
## 11. Wrap-up Checklist
164+
- [ ] Exit criteria satisfied
165+
- [ ] Verification evidence stored
166+
- [ ] Spec/Delta/Plan updated with lessons
167+
- [ ] Hand-off notes to next phase (if any)

0 commit comments

Comments
 (0)