Results for “document-query”

4 skills

Designs the contract for an API change inside one codebase — a component's props, a function surface, URL or query parameters, an event payload, or a module boundary — through a discovery pass, an options document with one recommendation, a question round, and an adversarial validation round, with every element of the contract justified from one stated goal. Use when you want to design, shape, decide, or nail down an interface, contract, signature, or API change for a capability you can already describe, sized for roughly one pull request. Produces a design document and changes no code. Does not specify what a feature should do — use plan-a-feature. Does not plan delivery or sequencing — use plan-implementation. Does not assess the architecture of existing code — use architectural-analysis. Does not write the code — use tdd. Does not restructure existing code — use refactor. Runs its rounds without pausing for review; to review each round as it lands, use pairing.

More results

grill-with-docs

Runs a structured interview that stress-tests a plan against the project's domain model, sharpens terminology, and updates CONTEXT.md and ADRs inline as decisions are made.

grill-with-docs

Stress-tests a plan against the project's domain model and documented decisions, sharpening terminology and updating DOMAIN.md and ADRs inline as decisions crystallize.

content-strategy

Plan documentation systems including information architecture, content audits, taxonomy design, content lifecycle management, and doc-as-code workflows. Use when organizing a documentation set, planning content structure, or designing navigation and discovery. Also trigger for 'information architecture', 'content audit', 'doc structure', 'taxonomy', 'content planning', 'documentation strategy', 'IA design', or 'sitemap'.