@sassywares/skills 0.6.9 → 0.6.10

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
@@ -51,13 +51,13 @@ Settled. Pick one:
51
51
  3. Implement and ship it via /sassy-lfg
52
52
  ```
53
53
 
54
- Pick 1 to get a plan file, then run one phase at a time:
54
+ Pick 1 to get a plan file. Plan then asks again with just the other two — start working on it, or implement and ship it — or you stop there and run it later, one phase at a time:
55
55
 
56
56
  ```text
57
57
  /sassy-work docs/plans/add-workspace-invitations.md
58
58
  ```
59
59
 
60
- Or take the whole plan through one session:
60
+ Or the whole plan through one session:
61
61
 
62
62
  ```text
63
63
  /sassy-lfg docs/plans/add-workspace-invitations.md
@@ -199,8 +199,8 @@ flowchart LR
199
199
  D -->|1. plan document| E[docs/plans/slug.md]
200
200
  D -->|2. start working| F[sassy-work]
201
201
  D -->|3. implement and ship| G[sassy-lfg]
202
- E --> F
203
- E --> G
202
+ E -->|then: start working| F
203
+ E -->|then: implement and ship| G
204
204
  F --> H[sassy-cycle]
205
205
  G --> H
206
206
  H --> I{Code approval}
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sassywares/skills",
3
- "version": "0.6.9",
3
+ "version": "0.6.10",
4
4
  "description": "Lean, explicit-invocation Agent Skills for shipping fast: plan, work, review, validate, ship.",
5
5
  "type": "module",
6
6
  "license": "MIT",
@@ -56,7 +56,15 @@ The user must pick explicitly. There is no default and no auto-selection. If no
56
56
 
57
57
  ### Option 1 — Write the plan
58
58
 
59
- Read `references/plan-format.md` and write the plan, including the per-phase manual QA tables that format defines. Then report the absolute path and STOP. No second menu, no "what next" prompt. Do not implement or commit.
59
+ Read `references/plan-format.md` and write the plan, including the per-phase manual QA tables that format defines. Then report the absolute path and offer the remaining two options, now run on the plan file:
60
+
61
+ ```text
62
+ Plan written to <absolute path>. Pick one, or stop here:
63
+ 1. Start working via /sassy-work
64
+ 2. Implement and ship it via /sassy-lfg
65
+ ```
66
+
67
+ Wait for the user. A pick loads that skill with the plan path as its argument — `sassy-work` runs the next phase, `sassy-lfg` runs every phase and ships. Anything else, or no human present, ends here with the plan written. Do not recommend one, and do not implement or commit before a pick.
60
68
 
61
69
  ### Option 2 — Start working via `sassy-work`
62
70