backprop
Turn a bug into a row and a check, so it cannot come back. Invoke when the user says "ds:backprop", "bug:", or reports a defect found after a dossier shipped.
- License 许可
- ISC
- 最近更新
- 2026-11-15
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- backprop
- description
- Turn a bug into a row and a check, so it cannot come back. Invoke when the user says "ds:backprop", "bug:", or reports a defect found after a dossier shipped.
- argument-hint
- <bug description>
03 SKILL.md 正文
ds:backprop
A bug is a row plus a check.
- Find the root cause with a
gathereragent. Ask for exact lines andfile:line. - Write a check that fails today because of the bug. Add it to
## Checks. If it must hold for good, mark it a guard. ds add "Fix <bug>". Plan its commit in## Commits, and tie the check to the row.- If the plan was already checked, run the plan steps again from
ds lint(see/dossier:plan). - Build it with
/dossier:build.
With no live dossier, add the row to the register with ds add "<title>" --register and start a dossier for it with /dossier:plan.
04 同仓库更多 Skills
ship
Review the dossier branch once, fold the fixup commits into the planned commits, hand the push and PR to the operator, then watch CI. Invoke when the user says "ds:ship", "ship the dossier", or when ds next exits 4.
plan
Open a dossier and write its plan with the operator, then get it checked by a fresh agent before any build. Invoke when the user says "ds:plan", "start a dossier", "plan this", "grill me" in a repo with `.scratchpad/dossier/`, or when work needs more than one commit.
suite-review
Run the monthly evidence review of this repo's plugin skills. Count each skill's opportunities and uses with the census, read what happened where a skill was not used, put each skill in one bucket, act, and write the actions as predictions with a check date. Use when the operator says "suite review" or "monthly review", or when the suite-review line on LATER.md is due.
research-report
Research a technical question with probes on the local system, a web fan-out through deep-research, a grounding pass on every load-bearing claim, and a report rendered as one HTML page. Use when the user asks for a research report, a design study or an evidence-backed recommendation about their own system.
html-report
Render a markdown report as one self-contained HTML page for a human reader, in plain English, with the answer first, a table of contents and Mermaid diagrams drawn as images. Use when the user asks for an HTML report, or for a readable page made from a markdown document.
domain-modeling
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.