skills/outcome/SKILL.md
Generates and updates .claude/OUTCOME.md interactively. When the file is absent or empty (no Behavior / all sections TBD), collects content via AskUserQuestion and writes the stub; when present, shows the current state and applies updates.
npx skillsauth add thkt/claude-config outcomeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Generate or update .claude/OUTCOME.md interactively. This skill is also the landing point when another skill detects a missing OUTCOME.md. Interactive generation instead of hard-stop keeps new-repo bootstrap moving. Not proceeding on a mere warning prevents work from continuing against a vague outcome.
| State | Flow | | ------------------------------------------------ | -------- | | File absent, Behavior empty, or all sections TBD | Generate | | Otherwise | Update |
| Step | Action |
| ---- | --------------------------------------------------------------------------------------- |
| 1 | Read ${CLAUDE_SKILL_DIR}/templates/outcome.md (structure and examples) |
| 2 | Collect Behavior (≥1, subject named), Non-goals, Constraints via AskUserQuestion (3 Qs) |
| 3 | Run each Behavior through the Outcome test; rewrite failures and re-present |
| 4 | Fill the template and Write .claude/OUTCOME.md |
| Step | Action |
| ---- | ------------------------------------------------------------------- |
| 1 | Read .claude/OUTCOME.md and present the current three sections |
| 2 | Confirm which sections change and their content via AskUserQuestion |
| 3 | Run each changed Behavior through the Outcome test, then Edit |
Do not Write or Edit until every Behavior passes all four Outcome test checks.
development
Judge a SKILL.md against craft axes (single responsibility, description distinctiveness, imperative voice, verifiable completion, calibration, progressive disclosure) and apply the fixes the audit surfaces. Do not use for format-presence-only checks (use reviewer-prompt) or reproducibility loops (use /tuning).
tools
Internal helper for /think Step 11. Renders SOW.md + Spec.md as an integrated Astro view and returns a dev server URL.
development
Extract repository spec while detecting bugs, spec gaps, and consistency drift via dual-purpose documentation. OUTCOME.md-axis question-driven exploration with ephemeral output. Do NOT use for code review (use /audit or /polish), feature implementation (use /code), planning only (use /think), or single-bug fix (use /fix).
development
Discover undocumented design decisions and challenge each candidate via critic-design before promotion. Rank by impact and reversibility, produce ADR promotion candidates. Treat each candidate as a position arguing for ADR status, not a fact to be filed. Pairs with audit-adr-drift, which scans existing ADRs for drift against code.