@sassywares/skills 0.6.8 → 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/CONCEPTS.md CHANGED
@@ -54,7 +54,7 @@ A durable document under `docs/plans/` with intent, decisions, constraints, phas
54
54
 
55
55
  ## Brief
56
56
 
57
- A settled in-context brief produced by `sassy-plan` when the user picks "build it, commit, and stop" (`sassy-work`) or "build it and ship" (`sassy-lfg`). It carries the goal, decisions, constraints, work, and done-when, but no plan file and no QA tables.
57
+ A settled in-context brief produced by `sassy-plan` when the user picks "start working" (`sassy-work`) or "implement and ship" (`sassy-lfg`). It carries the goal, decisions, constraints, work, and done-when, but no plan file and no QA tables.
58
58
 
59
59
  ## Handoff
60
60
 
package/README.md CHANGED
@@ -46,18 +46,18 @@ That discussion settles the work, then offers a pick:
46
46
 
47
47
  ```text
48
48
  Settled. Pick one:
49
- 1. Write the plan — docs/plans/<slug>.md, run it later phase by phase
50
- 2. Build it, commit, and stop — runs sassy-work, no PR
51
- 3. Build it and ship — runs sassy-lfg: commit, PR, babysit
49
+ 1. Write the plan — docs/plans/<slug>.md
50
+ 2. Start working via /sassy-work
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
@@ -82,7 +82,7 @@ Debugging:
82
82
 
83
83
  | Skill | What it does |
84
84
  |---|---|
85
- | **`sassy-plan`** | Grills you one question at a time through every branch of the work — pushing back, assuming nothing, sketching UI on request — until nothing is open, then offers three choices: write the plan, build and commit via `sassy-work`, or build and ship via `sassy-lfg`. |
85
+ | **`sassy-plan`** | Grills you one question at a time through every branch of the work — pushing back, assuming nothing, sketching UI on request — until nothing is open, then offers three choices: write the plan, start working via `sassy-work`, or implement and ship via `sassy-lfg`. |
86
86
  | **`sassy-scout`** | Grounds an area on demand and writes the shared grounding brief other agents read instead of re-exploring. |
87
87
  | **`sassy-work`** | Executes exactly one plan phase, or one in-context brief, commits after code approval, then hands off the next phase — a brief stops before ship. |
88
88
  | **`sassy-lfg`** | Executes every phase of a plan, or one in-context brief, then closes out via `sassy-ship` after code approval. |
@@ -197,10 +197,10 @@ flowchart LR
197
197
  B --> C[Discussion]
198
198
  C --> D{3-option picker}
199
199
  D -->|1. plan document| E[docs/plans/slug.md]
200
- D -->|2. build, commit, stop| F[sassy-work]
201
- D -->|3. build and ship| G[sassy-lfg]
202
- E --> F
203
- E --> G
200
+ D -->|2. start working| F[sassy-work]
201
+ D -->|3. implement and ship| G[sassy-lfg]
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.8",
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",
@@ -3,8 +3,8 @@ name: sassy-plan
3
3
  description: >-
4
4
  Grill the user relentlessly about a piece of work, walking every branch of the
5
5
  decision tree until nothing is assumed or open, then let the user choose:
6
- write a plan document, build and commit (sassy-work), or build and ship
7
- (sassy-lfg).
6
+ write a plan document, start working via sassy-work, or implement and ship
7
+ via sassy-lfg.
8
8
  Sketches UI on request. No modes, no QA flags. Use when asked to brainstorm,
9
9
  scope, plan, or create a phased plan.
10
10
  argument-hint: "[feature description, requirements, or idea to scope]"
@@ -13,7 +13,7 @@ disable-model-invocation: true
13
13
 
14
14
  # Sassy Plan
15
15
 
16
- **Outcome:** a decision ledger with zero open items — every branch of the work resolved by the user, explicitly delegated by them, or explicitly deferred by them — then the user's explicit choice from three options: write a plan document, build and commit via `sassy-work`, or build and ship via `sassy-lfg`.
16
+ **Outcome:** a decision ledger with zero open items — every branch of the work resolved by the user, explicitly delegated by them, or explicitly deferred by them — then the user's explicit choice from three options: write a plan document, start working via `sassy-work`, or implement and ship via `sassy-lfg`.
17
17
 
18
18
  **Does not implement.** Planning never implements. Execution belongs to `sassy-work` or `sassy-lfg`, and only after the user picks.
19
19
 
@@ -47,22 +47,30 @@ Only when the read-back is confirmed with zero open items, present exactly these
47
47
 
48
48
  ```text
49
49
  Settled. Pick one:
50
- 1. Write the plan — <artifacts.plans>/<slug>.md, run it later phase by phase
51
- 2. Build it, commit, and stop — runs sassy-work, no PR
52
- 3. Build it and ship — runs sassy-lfg: commit, PR, babysit
50
+ 1. Write the plan — <artifacts.plans>/<slug>.md
51
+ 2. Start working via /sassy-work
52
+ 3. Implement and ship it via /sassy-lfg
53
53
  ```
54
54
 
55
55
  The user must pick explicitly. There is no default and no auto-selection. If no human is present to answer (rare, e.g. a scripted invocation), take option 2 and say so; every branch you resolved without the user is recorded as an assumption, never as a decision.
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
60
 
61
- ### Option 2 — Build it, commit, and stop (`sassy-work`)
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.
68
+
69
+ ### Option 2 — Start working via `sassy-work`
62
70
 
63
71
  Load the `sassy-work` skill with the settled brief as the work brief and its decisions / done-when as the intent reference. No plan file is written. It stops before ship.
64
72
 
65
- ### Option 3 — Build it and ship (`sassy-lfg`)
73
+ ### Option 3 — Implement and ship it via `sassy-lfg`
66
74
 
67
75
  Load the `sassy-lfg` skill the same way: the settled brief as the work brief, its decisions / done-when as the intent reference. No plan file is written.
68
76