Loading...
Loading...
Found 6,969 Skills
Use when starting any implementation task, feature request, bug fix, or refactoring work. Triggers on /plan command, before any code is written, when requirements need structured analysis, or when transitioning from brainstorming to implementation. Forces question-asking, approach comparison, and explicit approval before any code.
This skill should be used when the user has a written implementation plan to execute in a separate session with review checkpoints.
Meticulous CLI schema command for outputting the full CLI command structure as JSON. Use when you need to programmatically inspect available commands and their options, or when building tooling that drives the Meticulous CLI.
Git commit your ledger with a meaningful message. Tag month-end, quarter-end, and year-end closes. Maintains the audit trail. Use after any meaningful ledger change. CLEAR step: Meta
Use when changing CFO Stack ledger conventions, process docs, Beancount metadata rules, or canonical ledger/file layout guidance that should stay out of AGENTS.md.
Used when a feature has been implemented but lacks design documentation and implementation plans. Automatically generate documents conforming to /hi-brainstorm and /hi-ace formats based on existing code and git history.
Manage the lifecycle of ExecPlans — self-contained, living specifications for multi-step work. Creates plans in the correct format, enforces living section updates, and handles the active → completed transition. Use for any work expected to take more than one session or touching more than 3 files. Triggers: "create a plan", "write a plan", "start plan", "continue plan", "resume plan", "finish plan", "complete plan", multi-step features, refactors, or tasks spanning sessions.
Use this skill when the user discusses experiment design, ablations, training runs, evaluation, baselines, metrics, failures, or result interpretation that should be logged into Obsidian experiment and result notes.
Use when experiments complete to judge what claims the results support, what they don't, and what evidence is still missing. Codex MCP evaluates results against intended claims and routes to next action (pivot, supplement, or confirm). Use after experiments finish — before writing the paper or running ablations.