timbo2547
4 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.
timbo2547code-to-review
Stage 4 of the feature workflow. Use when every task in an implementation plan under docs/plans/ is ticked and the finished feature needs reviewing as a whole. Takes a plan path, diffs HEAD against the base commit recorded in the plan header, and reviews that diff along two axes in parallel sub-agents: Standards, meaning this repo's documented standards, a code smell baseline, and the CONTEXT.md glossary, and Spec, meaning the spec the plan names and the ADRs that spec lists. Writes a report to
- installazioni
- 1
- GitHub Stars
- 0
- Aggiornato
- 5 set
timbo2547interview-to-specs
Stage 1 of the feature workflow. Use when an intent, idea, or rough plan exists but no spec has been written to disk yet. Interviews the user one question at a time, challenges the idea against the repo's glossary and recorded decisions, and produces a feature spec under docs/specs/ plus glossary updates in CONTEXT.md and any warranted ADRs. Also use when a downstream skill reports that no spec exists, or when a review shows the spec or an ADR was wrong. Do not use when a spec already exists and
- installazioni
- 1
- GitHub Stars
- 0
- Aggiornato
- 5 set
timbo2547plan-to-code
Stage 3 of the feature workflow. Use when an implementation plan exists under docs/plans/ and a specific task number from it should be implemented. Implements exactly one task per session: loads the plan header, the spec, and the ADRs that task cites, writes the code, then stops and tells the user which tests to run and what a passing result looks like. Ticks checkboxes and commits only after the user confirms those tests pass. Refuses to start without a task number, on a dirty working tree, or
- installazioni
- 1
- GitHub Stars
- 0
- Aggiornato
- 5 set
timbo2547specs-to-plan
Stage 2 of the feature workflow. Use when a written spec exists under docs/specs/ and no implementation plan has been written for it yet. Reads the spec, every ADR its front matter lists, and the CONTEXT.md glossary terms it depends on, then writes a task by task implementation plan to docs/plans/ with TDD steps, exact file paths, real code, the tests each task adds or affects, and a per task commit message. Refuses to run without a spec. Do not use to write the spec itself, which is interview-t
- installazioni
- 1
- GitHub Stars
- 0
- Aggiornato
- 5 set