@haposoft/cafekit 0.7.28 → 0.7.29
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.
package/README.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
> Claude Code-first spec-driven workflow and runtime bundle for AI coding assistants.
|
|
4
4
|
|
|
5
|
-
[](https://github.com/haposoft/cafekit)
|
|
6
6
|
[](LICENSE)
|
|
7
7
|
[](https://claude.ai/code)
|
|
8
8
|
|
|
@@ -128,9 +128,10 @@ The active workflow expects:
|
|
|
128
128
|
- design to define canonical contracts
|
|
129
129
|
- each task file to carry completion criteria and verification evidence
|
|
130
130
|
|
|
131
|
-
## Release Notes For 0.7.
|
|
131
|
+
## Release Notes For 0.7.29
|
|
132
132
|
|
|
133
133
|
This release is centered on Claude Code:
|
|
134
|
+
- fixed `hapo:develop` codebase scouting to call the bundled `inspector` agent instead of a non-existent `inspect` agent
|
|
134
135
|
- tightened `hapo:specs` state integrity and task finalization rules
|
|
135
136
|
- tightened `hapo:develop` definition-of-done and evidence-based quality gates
|
|
136
137
|
- bundled `hapo:generate-graph`
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@haposoft/cafekit",
|
|
3
|
-
"version": "0.7.
|
|
3
|
+
"version": "0.7.29",
|
|
4
4
|
"description": "Claude Code-first spec-driven workflow for AI coding assistants. Bundles CafeKit hapo: skills, runtime hooks, agents, and installer scaffolding.",
|
|
5
5
|
"author": "Haposoft <nghialt@haposoft.com>",
|
|
6
6
|
"license": "MIT",
|
|
@@ -57,7 +57,7 @@ You MUST NOT silently replace it with a simpler custom substitute ("for MVP", "p
|
|
|
57
57
|
|
|
58
58
|
| Thought (Excuse) | Reality (Rule) |
|
|
59
59
|
|-------------------|----------------|
|
|
60
|
-
| "No need to scout first" | Coding without knowing the architecture is blind. ALWAYS call `
|
|
60
|
+
| "No need to scout first" | Coding without knowing the architecture is blind. ALWAYS call the `inspector` agent to scan files. |
|
|
61
61
|
| "Review process is too tedious, let me just finish it myself" | The system needs an audit trail through agents. ALWAYS delegate via `Task` tool. |
|
|
62
62
|
|
|
63
63
|
## Absolute Workflow
|
|
@@ -66,7 +66,7 @@ You MUST NOT silently replace it with a simpler custom substitute ("for MVP", "p
|
|
|
66
66
|
flowchart TD
|
|
67
67
|
A["/hapo:develop \u003cfeature\u003e"] --> B[Step 1: Load Spec]
|
|
68
68
|
B -->|Missing| Z[Stop: Run /hapo:specs]
|
|
69
|
-
B -->|Ready| C[Step 2: Scout Codebase (
|
|
69
|
+
B -->|Ready| C[Step 2: Scout Codebase (inspector)]
|
|
70
70
|
C --> D[Step 3: Implement Code (god-developer)]
|
|
71
71
|
D --> E[Step 4: Quality Gate: Test + Review + Evidence]
|
|
72
72
|
E -->|Fail (code-auditor)| D
|
|
@@ -94,7 +94,7 @@ flowchart TD
|
|
|
94
94
|
- Before coding, set the active task(s) to `in_progress` in both markdown and `spec.json.task_registry`, or route through `/hapo:sync` if the runtime expects the sync protocol.
|
|
95
95
|
|
|
96
96
|
### Step 2: Scout (Codebase Inspection)
|
|
97
|
-
- **Mandatory:** Call agent `Task(subagent_type="
|
|
97
|
+
- **Mandatory:** Call agent `Task(subagent_type="inspector", ...)` to scan the overall codebase structure (e.g., where components live, where utils are). Avoid wandering into forbidden zones.
|
|
98
98
|
|
|
99
99
|
### Step 3: Implement Code
|
|
100
100
|
- Act as `god-developer` OR directly write code, executing tasks specified in the loaded Markdown file(s) sequentially.
|
|
@@ -10,7 +10,7 @@ Task(subagent_type="[agent-name]", prompt="[task description]", description="[sh
|
|
|
10
10
|
|
|
11
11
|
## Codebase Inspection Phase
|
|
12
12
|
```
|
|
13
|
-
Task(subagent_type="
|
|
13
|
+
Task(subagent_type="inspector", prompt="Scan and identify all files related to [feature-name] in the current codebase.", description="Scout [feature-name]")
|
|
14
14
|
```
|
|
15
15
|
|
|
16
16
|
## Code Implementation Phase
|