Loading...
Loading...
Found 3,082 Skills
Writes, validates, and converts ProductSpec files (.product-spec.md), the Markdown format for recording product intent before implementation. Use when authoring a new Product Spec, converting an existing PRD or feature doc into one, validating spec files locally or in CI, or recording how a spec's intent changed over time in a Decision Trace. For implementing code against a Product Spec that already exists, use the productspec skill instead.
Use when turning a requirement, spec, or feature brief into a single self-contained HTML design document in a fixed house style — one styled HTML page with a table-of-contents, architecture/sequence SVG diagrams, code/SQL/YAML blocks, callout boxes, an aligned-decisions (已对齐结论) panel, test cases, and a code index. Reuse for any new 需求/设计文档 that should look identical every time.
Generate a design document (design proposal) from a PRD, following the style of Go's official design proposals — structured with Abstract / Background / Design / Rationale / Compatibility / Implementation sections, with a strong focus on the 'why' behind decisions and tradeoffs. Trigger keywords: to-design, prd-to-design, PRD to design document, generate design document, write design document, design doc, design proposal, design proposal, technical design document.
Work out and record the architecture decisions that keep separately built parts of a system consistent, in a short architecture document. Creates, updates, or validates one; works from a spec, a raw idea, or an existing codebase. Use when the user says "create the architecture", "create technical architecture", "architecture spine", or "create a solution design"
Generates a structured implementation report reflecting on a just-completed feature — what was done, divergences, challenges. Use right after finishing an implementation, as the input to a system review.
Create audience-aware standalone application release notes and actionable migration guides from version-control changes, contracts, schemas, configuration, tests, and deployment evidence. Use for release-visible behavior, breaking changes, upgrades, deprecations, rollout steps, or rollback guidance.
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md, or recording or editing an ADR.
1. Requirement Gathering
Patterns for writing clear, consistent API field descriptions including types, constraints, examples, and edge cases.
Plan Requirements - generates a structured requirements document, asking clarifying questions about ambiguities before proceeding