@relipa/ai-flow-kit 0.0.7 → 0.0.8-beta.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.
Files changed (21) hide show
  1. package/README.md +7 -6
  2. package/bin/aiflow.js +400 -360
  3. package/bin/ak.js +4 -0
  4. package/custom/skills/generate-spec/SKILL.md +1 -6
  5. package/custom/templates/php-plain.md +261 -261
  6. package/custom/templates/php.md +261 -0
  7. package/custom/templates/python.md +79 -0
  8. package/docs/common/CHANGELOG.md +53 -1
  9. package/docs/common/QUICK_START.md +57 -50
  10. package/docs/common/cli-reference.md +161 -196
  11. package/docs/common/getting-started.md +3 -3
  12. package/docs/common/troubleshooting.md +7 -7
  13. package/package.json +2 -1
  14. package/scripts/checkpoint.js +46 -46
  15. package/scripts/gitnexus-worker.js +94 -94
  16. package/scripts/hooks/block-git-write.js +52 -0
  17. package/scripts/hooks/session-stop.js +55 -55
  18. package/scripts/init.js +27 -5
  19. package/scripts/task.js +21 -0
  20. package/scripts/use.js +880 -625
  21. package/upstream/skills/brainstorming/SKILL.md +3 -3
package/upstream/skills/brainstorming/SKILL.md CHANGED
@@ -26,7 +26,7 @@ You MUST create a task for each of these items and complete them in order:
26
26
  3. **Ask clarifying questions** — one at a time, understand purpose/constraints/success criteria
27
27
  4. **Propose 2-3 approaches** — with trade-offs and your recommendation
28
28
  5. **Present design** — in sections scaled to their complexity, get user approval after each section
29
- 6. **Write design doc** — save to `docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md` and commit
29
+ 6. **Write design doc** — save to `docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md`
30
30
  7. **Spec self-review** — quick inline check for placeholders, contradictions, ambiguity, scope (see below)
31
31
  8. **User reviews written spec** — ask user to review the spec file before proceeding
32
32
  9. **Transition to implementation** — invoke writing-plans skill to create implementation plan
@@ -111,7 +111,7 @@ digraph brainstorming {
111
111
  - Write the validated design (spec) to `docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md`
112
112
  - (User preferences for spec location override this default)
113
113
  - Use elements-of-style:writing-clearly-and-concisely skill if available
114
- - Commit the design document to git
114
+ - Do NOT run `git add` or `git commit` for the design document — the developer commits manually.
115
115
 
116
116
  **Spec Self-Review:**
117
117
  After writing the spec document, look at it with fresh eyes:
@@ -126,7 +126,7 @@ Fix any issues inline. No need to re-review — just fix and move on.
126
126
  **User Review Gate:**
127
127
  After the spec review loop passes, ask the user to review the written spec before proceeding:
128
128
 
129
- > "Spec written and committed to `<path>`. Please review it and let me know if you want to make any changes before we start writing out the implementation plan."
129
+ > "Spec written to `<path>`. Please review it and let me know if you want to make any changes before we start writing out the implementation plan."
130
130
 
131
131
  Wait for the user's response. If they request changes, make them and re-run the spec review loop. Only proceed once the user approves.
132
132