drwil-progress
Generate a static HTML dashboard (project progress, contract coverage) with nothing to deploy. Use for a quick overview before a meeting, resuming a project, or a review.
- License 许可
- MIT
- 所属仓库
- wdubilly/drwil
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- drwil-progress
- description
- Generate a static HTML dashboard (project progress, contract coverage) with nothing to deploy. Use for a quick overview before a meeting, resuming a project, or a review.
03 SKILL.md 正文
Recipe: docs/recipes/view-progress.md (copy the optional module from
templates/common/optional/dashboard/ to
.githooks/dashboard.mjs (to create), run it by hand with
node .githooks/dashboard.mjs, never in CI or at commit time).
Nothing is recomputed: the dashboard copies the "Status" line and increments as
written in each docs/projects/ brief.
04 同仓库更多 Skills
drwil-progress
Generate a static HTML dashboard (project progress, contract coverage) with nothing to deploy. Use for a quick overview before a meeting, resuming a project, or a review.
drwil-usage
Measure the tokens consumed per workstream and record the closing workstream's line in .drwil/usage.jsonl. Use when closing a workstream, or when asked what a workstream cost, to feed the dashboard and the analysis reports.
drwil-start
Start a workstream, or a queue of workstreams, with one human gesture — open a poll of the scoped briefs; the human's answer, read by the tool, moves governance to BUILD (when several briefs are chosen, the next ones are queued and started by the agent after each closing). Use when the human wants to start implementing one or several briefs.
drwil-scope
At the end of a scoping pushed (brief or intention committed on a scoping branch, its PR open), set its PR to automatic merge with the tool, without a poll — the automatic merge is the default behaviour. Use when a scoping is pushed and its PR opened, or when the human runs /drwil-scope.
run-locally
Run the project locally for development — prerequisites, success signals, known pitfalls on first startup.
refactor-without-breaking
Split or restructure existing code without changing its behavior — characterization tests first, small committed steps, bugs found committed separately. Use for every refactor.