edkuksa/skills
1
0
Fork 0
mirror of https://github.com/mattpocock/skills.git synced 2026-07-29 02:52:42 +07:00
Code Issues Packages Projects Releases Wiki Activity

refactor(to-plan,to-issues): prune no-ops in vertical-slice framing

Browse Source 
Fold the redundant 'thin vertical slice cuts through all layers, NOT
horizontal' intro sentence into vertical-slice-rules bullet 1 (it was
duplicating the bullet), and cut to-plan's 'no parallelism / top-to-bottom'
restatement — 'sequential' is already anchored as the leading word. Keeps
the shared core identical across the two sibling skills.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Matt Pocock
2026-07-08 14:13:21 +01:00
co-authored by Claude Opus 4.8
parent 93f73198e3
commit c5a4a8c2e9
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/engineering/to-plan/SKILL.md
+3 -3
View File
@@ -26,18 +26,18 @@ Look for opportunities to prefactor the code to make the implementation easier.
### 3. Draft vertical slices ### 3. Draft vertical slices
Break the work into **tracer bullet** phases. Each phase is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer. Break the work into **tracer bullet** phases.
<vertical-slice-rules> <vertical-slice-rules>
- Each slice delivers a narrow but COMPLETE path through every layer (schema, API, UI, tests) - Each slice cuts a narrow but COMPLETE path through every layer (schema, API, UI, tests) — vertical, NOT a horizontal slice of one layer
- A completed slice is demoable or verifiable on its own - A completed slice is demoable or verifiable on its own
- Each slice is sized to fit in a single fresh context window - Each slice is sized to fit in a single fresh context window
- Any prefactoring should be done first - Any prefactoring should be done first
</vertical-slice-rules> </vertical-slice-rules>
Order the phases **sequentially**, in dependency order — each phase builds on the ones before it. There is no parallelism: a plain top-to-bottom sequence. Order the phases in dependency order — each builds on the ones before it.
### 4. Quiz the user ### 4. Quiz the user