Some blockers are neither a decision, a prototype, nor research — just literal manual work (moving data, signing up for a service, provisioning access) that must happen before discussion can move forward. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| decision-mapping | ||
| loop-me | ||
| review | ||
| wizard | ||
| writing-beats | ||
| writing-fragments | ||
| writing-shape | ||
| README.md | ||
In Progress
Skills that are still being developed. They're not ready to ship — expect rough edges, breaking changes, and abandoned experiments. They're excluded from the plugin and the top-level README until they graduate to a stable bucket.
- decision-mapping — Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time. User-invoked.
- loop-me — Grill yourself into implementable workflow specs over multiple sessions, using the current directory as a stateful workspace. User-invoked.
- review — Review changes since a fixed point along two parallel axes: Standards (does the diff follow the repo's coding standards?) and Spec (does the diff faithfully implement the originating issue/PRD?).
- wizard — Generate an interactive bash wizard that walks a human through a manual procedure (setup, a one-off migration, a state transition) — opening URLs, capturing values, writing
.envand GitHub Actions secrets. User-invoked. - writing-beats — Shape an article as a journey of beats, choose-your-own-adventure style. Pick a starting beat, write only that beat, then pivot to the next, until the article reaches a natural end.
- writing-fragments — Grilling session that mines you for fragments — heterogeneous nuggets of writing — and appends them to a single document as raw material for a future article.
- writing-shape — Take a markdown file of raw material and shape it into an article paragraph by paragraph, arguing format choices at each step.