doc-driven

Installation
SKILL.md

Documentation-driven development

Update concise product docs first, review the documentation diff, then implement the approved behavior. The docs are the specification; separate specs, issues, and implementation plans are unnecessary.

Start here

  1. Read repository instructions, README, structure, and existing docs. Product docs need an overview linked to the product's actual areas; a README alone or generated output is insufficient.
  2. For initial docs, or an invocation without a stage when no product docs exist, follow setup.md. Document existing behavior and stop for review; leave implementation unchanged.
  3. Otherwise use specify or implement as requested. If the stage or area is unclear, ask. Reuse existing docs.
  4. Implementation requires explicit approval of the relevant documentation changes and an explicit implement request. Missing docs or approval are blockers.

Find the scope

Read the index, affected docs, and linked shared rules. Follow relevant references without rereading cycles, and search incoming links and implementation consumers. Clarify uncertainties affecting behavior, permissions, or acceptance before treating them as requirements.

Documentation convention

Installs
2
Repository
dbpolito/skills
First Seen
Nov 4, 2026