design-feature

Turn an idea or a feature request into an exhaustive, checkable product definition — the stage before engineering planning. The core mechanism is capability closure: a checklist that forces every entity, capability, and role a feature introduces to be walked to its full surface (CRUD + state transitions + UI entry point + API + test, or an explicit design-time n/a), so non-frontier executor models stop silently omitting the implicit work ("auth with dashboard management and ACLs" must not collapse to a users table + a list view). Closure has three fixed checklists: entity closure (each entity to full surface), integration closure (the feature reconciled against every subsystem in the project's capability inventory, docs/CAPABILITIES.md — auth, ACL, navigation, notifications, …), and the role matrix (every inventory role explicitly allowed/denied per capability) — plus an expectation sweep that forces what a competent human would implicitly assume ("a blog has drafts") into in-scope/out-of-scope/deferred, never left unstated. Writes the SPEC's product half and stamps the ## Design status: designed marker plan-feature reads before it will plan a feature's engineering half. Bare design-feature <slug> reviews and asks what to change; design-feature <slug> <instruction> applies a change directly. On Claude Code and want hand-tuned per-skill model/effort tiers? Install the #claude branch instead (npx skills add gtrabanco/agentic-workflow#claude) — see the README. This branch is model-agnostic: the skill inherits whatever model and effort your agent session is already using. Triggers: "add feature", "add a feature", "new feature", "design a feature", "design the product half of NN", "capability closure for NN", "define the feature before planning it".