@haposoft/cafekit 0.8.3 → 0.8.4
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/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@haposoft/cafekit",
|
|
3
|
-
"version": "0.8.
|
|
3
|
+
"version": "0.8.4",
|
|
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",
|
|
@@ -187,6 +187,7 @@ specs/<feature>/
|
|
|
187
187
|
- Update `spec.json` with `"status": "in_progress"` and `"current_phase": "develop"`
|
|
188
188
|
- Ensure `task_files` + `task_registry` are synchronized and `ready_for_implementation` reflects the finalization audit outcome
|
|
189
189
|
- Report the spec directory path to the orchestrator
|
|
190
|
+
- The only valid implementation handoff is `/hapo:develop <feature>` (or `/hapo:develop <feature> <task-file>` for a single task). Never suggest `/work`, `/code`, or an unnamed "orchestrator dispatch" command.
|
|
190
191
|
- DO NOT begin implementation yourself
|
|
191
192
|
|
|
192
193
|
## Integration Points
|
|
@@ -346,6 +346,8 @@ Load: `references/review.md` + `rules/design-review.md`
|
|
|
346
346
|
### Step 10: Completion — Context Reminder (MANDATORY)
|
|
347
347
|
After completing the spec, output a short summary of what was generated, then you MUST output the following block EXACTLY as written. DO NOT use awkward translations like "Điểm đã phản ánh đúng quyết định của bạn", keep it professional or just output the block directly:
|
|
348
348
|
|
|
349
|
+
**Command integrity:** The implementation handoff command is always `/hapo:develop <feature>`. Never suggest `/work`, `/code`, or any non-CafeKit alias as the next step for this workflow.
|
|
350
|
+
|
|
349
351
|
```
|
|
350
352
|
✅ Spec complete: specs/<feature>/
|
|
351
353
|
📌 Next step — run:
|