catalyst-os 1.1.0 → 1.1.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -1,6 +1,12 @@
|
|
|
1
1
|
# /approve-spec
|
|
2
2
|
|
|
3
|
-
Accept
|
|
3
|
+
Accept a **fully built and validated** implementation — commit, archive, and propagate learnings.
|
|
4
|
+
|
|
5
|
+
> **Lifecycle position:** This is the FINAL step. Only use after `/build-spec` and `/validate-spec` have completed successfully.
|
|
6
|
+
>
|
|
7
|
+
> **Flow:** `/catalyze-spec` → `/build-spec` → `/validate-spec` → **`/approve-spec`**
|
|
8
|
+
>
|
|
9
|
+
> **This is NOT for approving a spec/plan before building.** There is no "approve plan" step — after catalyzing, you go straight to `/build-spec`.
|
|
4
10
|
|
|
5
11
|
## Usage
|
|
6
12
|
|
|
@@ -12,10 +12,16 @@ Final verification, git commit, spec archival, self-documentation (propagate lea
|
|
|
12
12
|
- `verification-before-completion` — Final TDD compliance check
|
|
13
13
|
- `agent-delegation` — Scribe delegation for library extraction
|
|
14
14
|
|
|
15
|
-
## Prerequisites
|
|
15
|
+
## Prerequisites — HARD GATES
|
|
16
16
|
|
|
17
|
-
|
|
18
|
-
- `
|
|
17
|
+
> **This skill is the FINAL step in the spec lifecycle.** It runs ONLY after build and validation are complete.
|
|
18
|
+
> **Flow:** `/catalyze-spec` → `/build-spec` → `/validate-spec` → **`/approve-spec`** (you are here)
|
|
19
|
+
>
|
|
20
|
+
> If the spec has not been built yet, STOP and tell the user to run `/build-spec` first.
|
|
21
|
+
> If the spec has not been validated yet, STOP and tell the user to run `/validate-spec` first.
|
|
22
|
+
|
|
23
|
+
- `/build-spec` must have been completed (tasks.md exists with completed tasks)
|
|
24
|
+
- Validation must be complete (`validation.md` must show all checks passed)
|
|
19
25
|
- `handoff.md` must exist
|
|
20
26
|
- TDD compliance verified
|
|
21
27
|
|
|
@@ -173,5 +173,9 @@ REMINDER: /build-spec follows strict TDD
|
|
|
173
173
|
3. Then implement (Builders)
|
|
174
174
|
4. Tests must PASS (green phase)
|
|
175
175
|
|
|
176
|
-
Next:
|
|
176
|
+
Next steps:
|
|
177
|
+
- /build-spec @YYYY-MM-DD-{slug} to start TDD build
|
|
178
|
+
- Or /iterate-spec if you want changes first
|
|
177
179
|
```
|
|
180
|
+
|
|
181
|
+
**IMPORTANT: Do NOT suggest `/approve-spec` after spec shaping.** `/approve-spec` is only for accepting a fully built and validated implementation — it is the FINAL step, not a plan-approval step. The correct flow is: `/catalyze-spec` → `/build-spec` → `/validate-spec` → `/approve-spec`.
|