@fernado03/zoo-flow 0.7.10 → 0.7.11

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,7 +1,7 @@
1
1
  {
2
2
  "name": "@fernado03/zoo-flow",
3
3
  "description": "Workflow control plane for Zoo Code.",
4
- "version": "0.7.10",
4
+ "version": "0.7.11",
5
5
  "type": "module",
6
6
  "bin": {
7
7
  "zoo-flow": "bin/zoo-flow.js"
@@ -16,7 +16,7 @@ Issue tracker + label vocabulary should exist; run `/setup-matt-pocock-skills` i
16
16
  5. Present numbered breakdown: title; `HITL`/`AFK`; blockers; user stories.
17
17
  6. Ask user to validate granularity/deps/HITL/AFK/merge/split.
18
18
  7. Iterate until approved.
19
- 8. Publish in dependency order.
19
+ 8. Publish to issue tracker (or `.scratch/{feature-slug}/issues/` for local tracker).
20
20
  9. Apply `ready-for-agent` label unless instructed otherwise.
21
21
  10. DO NOT close/modify parent issue.
22
22
 
@@ -15,7 +15,7 @@ RULE: Do not interview user. Synthesize current context.
15
15
  2. Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can.
16
16
  3. Check with the user that these seams match their expectations.
17
17
  4. Write PRD.
18
- 5. Publish to issue tracker.
18
+ 5. Publish to issue tracker (or `.scratch/{feature-slug}/PRD.md` for local tracker).
19
19
  6. Apply `ready-for-agent`.
20
20
 
21
21
  ## PRD template