@sassywares/skills 0.6.7 → 0.6.8

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 "start working now" or "take it all the way". 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 "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.
58
58
 
59
59
  ## Handoff
60
60
 
package/README.md CHANGED
@@ -46,9 +46,9 @@ That discussion settles the work, then offers a pick:
46
46
 
47
47
  ```text
48
48
  Settled. Pick one:
49
- 1. Write it to docs/plans/<slug>.md
50
- 2. Start working now — stop before ship
51
- 3. Take it all the way — run it, ship it, babysit the PR
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
52
52
  ```
53
53
 
54
54
  Pick 1 to get a plan file, then run one phase at a time:
@@ -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, start working now, or take it all the way to a PR. |
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`. |
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,8 +197,8 @@ 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. start working| F[sassy-work]
201
- D -->|3. take it all the way| G[sassy-lfg]
200
+ D -->|2. build, commit, stop| F[sassy-work]
201
+ D -->|3. build and ship| G[sassy-lfg]
202
202
  E --> F
203
203
  E --> G
204
204
  F --> H[sassy-cycle]
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sassywares/skills",
3
- "version": "0.6.7",
3
+ "version": "0.6.8",
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,7 +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, start working now, or take it all the way to a PR.
6
+ write a plan document, build and commit (sassy-work), or build and ship
7
+ (sassy-lfg).
7
8
  Sketches UI on request. No modes, no QA flags. Use when asked to brainstorm,
8
9
  scope, plan, or create a phased plan.
9
10
  argument-hint: "[feature description, requirements, or idea to scope]"
@@ -12,7 +13,7 @@ disable-model-invocation: true
12
13
 
13
14
  # Sassy Plan
14
15
 
15
- **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 now, or take it all the way to a PR.
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
17
 
17
18
  **Does not implement.** Planning never implements. Execution belongs to `sassy-work` or `sassy-lfg`, and only after the user picks.
18
19
 
@@ -46,9 +47,9 @@ Only when the read-back is confirmed with zero open items, present exactly these
46
47
 
47
48
  ```text
48
49
  Settled. Pick one:
49
- 1. Write it to <artifacts.plans>/<slug>.md
50
- 2. Start working now — stop before ship
51
- 3. Take it all the way — run it, ship it, babysit the PR
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
52
53
  ```
53
54
 
54
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.
@@ -57,11 +58,11 @@ The user must pick explicitly. There is no default and no auto-selection. If no
57
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
60
 
60
- ### Option 2 — Start working now
61
+ ### Option 2 — Build it, commit, and stop (`sassy-work`)
61
62
 
62
63
  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.
63
64
 
64
- ### Option 3 — Take it all the way
65
+ ### Option 3 — Build it and ship (`sassy-lfg`)
65
66
 
66
67
  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.
67
68
 
@@ -81,7 +81,7 @@ When the argument is not a plan path, it is one settled brief:
81
81
  2. Run one `sassy-cycle` with the brief as the work brief and its decisions / done-when as the intent reference. Do not split it into multiple cycles.
82
82
  3. Present the code approval gate with no QA checklist, and wait. Changes requested → a rework cycle with the changes as findings and the brief's decisions / done-when as the intent reference, then this gate again; `blocked` stops.
83
83
  4. On code approval, persist the brief's changes the same way the plan path does: a `sassy-commit` delegation with `branch:current` in a remote repo, or the workspace snapshot in a workspace.
84
- 5. Stop and report. Shipping is a separate step (`sassy-ship`), or `sassy-lfg` would have taken it all the way. Never create or update a plan file.
84
+ 5. Stop and report. Shipping is a separate step (`sassy-ship`), or `sassy-lfg` would have built and shipped it. Never create or update a plan file.
85
85
 
86
86
  ## Hard rules
87
87