skills.rest
kreek
kreekCOMMUNITY
Explore all skills by this author →
GitHub

specify

Guides collaborative design decisions before implementation through discovery, tradeoffs, and ADRs.

1|Updated Apr 24, 2026
Search Tags:#design#adr#rfc#human-in-the-loop#tech spec#architecture decision#tradeoffs
One-click install
npx skills add https://github.com/kreek/consult --skill specify-kreek
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: specify
Source: https://github.com/kreek/consult/tree/main/plugin/skills/specify
Command: npx skills add https://github.com/kreek/consult --skill specify-kreek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Ambiguous or high-stakes engineering work often gets coded before the design is agreed, producing expensive rework on public interfaces, data models, and structural dependencies. This Skill turns fuzzy intent into an agreed design direction before any code is written. ## Core Features & Use Cases - Design-Partner Workflow: The agent reads the current codebase, cites surfaces with file:line evidence, and proposes concrete options the human approves, revises, or rules out. - Decision Artifacts: Produces ADRs, RFCs, tech specs, and design notes capturing what was actually approved, stored in checked-in docs. - Scoped Gating: Asks one decision question at a time only for expensive-to-reverse choices like contracts, data shapes, and structural dependencies. - Use Case: Before adding a new public API module, use this Skill to review the existing surface, propose a target shape with tradeoffs, and record the agreed direction in an ADR. ## Quick Start Use the specify skill to turn this feature idea into an agreed design direction with tradeoffs before writing any code.

Frequently Asked Questions about specify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write an ADR or RFC before coding a feature?▼

Frame the decision that needs agreement, read the current code surface, then propose one recommended option with its key tradeoff. Record only what the human approved in a checked-in docs file, keeping the artifact as small as useful.

When should I use a design skill versus a task planning workflow?▼

Use design-first when work touches contracts, module boundaries, state transitions, or structural dependencies. Once the direction is agreed, hand off to a planning workflow for file-by-file sequencing and task checklists.

What counts as a contract in software design review?▼

A contract is any caller-facing boundary: function signatures, module exports, public types, error vocabularies, CLI flags, environment variables, schemas, migrations, event payloads, file formats, and config keys, not just HTTP APIs.

When should I skip the design phase for a code change?▼

Skip it for typos, docs-only edits, internal helper extraction, private file moves, dependency bumps without public surface changes, and narrow bug fixes restoring intended behavior. Low-stakes disposable work runs without gates.

Does an approved design document approve the concrete interfaces?▼

No. An approved design or RFC approves the direction only. Concrete interfaces and domain shapes still need separate contract and domain-modeling sign-off at build time, with each surface marked approved or proposed.

Related Skills

Explore More Software Engineering Skills→
brandtambrandtam
2

to-prd

Generates a PRD from conversation context and publishes it to the project issue tracker.

Community
Intermediate
cookeyholdercookeyholder

test-driven-development

Write failing tests before implementation to enforce a red-green-refactor workflow.

Community
Intermediate
mikivujkovicmikivujkovic

ddd-playbook

Orchestrate DDD discovery for the ToDo domain with bounded contexts and invariants.

Community
Basic
WeWake1WeWake1

gsd-add-tests

Generates unit and E2E tests for a completed phase from UAT criteria and implementation files.

Community
Intermediate