ask-demon
Ask Demon
You don't remember every skill, so ask. This pack complements Matt's engineering skills: Matt owns the engineering loop (grill → spec → tickets → implement → code-review — the single review entry point) and the writing skills; this pack owns the documentation and Agent-Note maintenance loop and game-domain work. The full absorption map and seams are in the pack's skills map (docs/skills-map.md in the source repository).
A flow is a path through the skills. One main flow carries the documentation work; a governance run brings a whole repository's docs in line with its standard; everything else is standalone, or a prose-and-docs tool layer that runs underneath.
Session discipline
Five standing-order lines in the host repository's root AGENTS.md govern every action; setup-demon-skills writes them into a repository. Operationally:
- Before acting — answer questions and analyze proposals without writing; treat only an explicit execution signal with a confirmed scope as authorization; unclear intent gets one clarifying question first.
- Before committing — a failed check blocks the commit; the fix or its explanation ships in the same turn, and the final report names each failed check.
- Before claiming — inspect files before editing or describing them; report only verified reading and completed work.
- Before destructive moves — deletions, history rewrites, and force-push require the user to name the action before it runs.
- When delegating — keep bounded work local and reuse valid context; delegate independent expensive work only when the parallel saving beats dispatch and context reconstruction; cap active subagents at three, descendants included; prioritize fixes and acceptance at the real entry point.
Every flow in this pack obeys the gate: findings and plans come first, fixes run after confirmation.