@ericrisco/rsc 0.1.30 → 0.1.31
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/manifest.json +1 -1
- package/package.json +1 -1
- package/skills/plan/SKILL.md +17 -4
package/manifest.json
CHANGED
package/package.json
CHANGED
package/skills/plan/SKILL.md
CHANGED
|
@@ -200,9 +200,22 @@ what changed — don't fork a `-v2`.
|
|
|
200
200
|
`../postgresdb/SKILL.md`).
|
|
201
201
|
- Project-wide non-negotiables (stack canon, quality bars) → `../constitution/SKILL.md`.
|
|
202
202
|
|
|
203
|
+
## Always propose isolation before the build
|
|
204
|
+
|
|
205
|
+
Once the plan is written, **always propose isolating the work in a git worktree/branch** before
|
|
206
|
+
any code is implemented — every feature, not just the risky ones. One line, calibrated to the dial:
|
|
207
|
+
|
|
208
|
+
> *"Antes de implementar, ¿aíslo este trabajo en un worktree/rama propia (`../worktrees/SKILL.md`)
|
|
209
|
+
> para no tocar tu rama actual? (recomendado)"*
|
|
210
|
+
|
|
211
|
+
Propose it here at the plan→build boundary so the decision is made before `implement` writes a line.
|
|
212
|
+
If the user accepts, hand to `../worktrees/SKILL.md` first; if they decline, note it and continue.
|
|
213
|
+
If you are already on the default branch (`main`/`master`), isolation is **not** optional — say so
|
|
214
|
+
and route to `worktrees` regardless. (`implement` re-checks this as a hard gate before its first commit.)
|
|
215
|
+
|
|
203
216
|
## Next in the chain
|
|
204
217
|
|
|
205
|
-
Plan written, indexed, decisions logged →
|
|
206
|
-
sequencing section into an ordered, independently-verifiable
|
|
207
|
-
If planning surfaced an ambiguity the spec never resolved,
|
|
208
|
-
before tasking.
|
|
218
|
+
Plan written, indexed, decisions logged → propose isolation (above), then hand off to
|
|
219
|
+
**`../tasks/SKILL.md`**, which turns the sequencing section into an ordered, independently-verifiable
|
|
220
|
+
task list with a done-check per task. If planning surfaced an ambiguity the spec never resolved,
|
|
221
|
+
loop back to **`../clarify/SKILL.md`** before tasking.
|