Results for “specification”

Generate comprehensive Product Requirements Documents (PRDs) for software systems and AI-powered features, including executive summaries, user stories, technical specifications, and risk analysis.

Conducts structured requirements workshops to produce feature specifications, user stories, EARS-format functional requirements, acceptance criteria, and implementation checklists.

Enforces a machine-readable behavioral contract for multi-agent development, mandating specification-first workflows, git checkpoints, context lineage, and quality gates.

Generates a candid improvement report for a software requirements specification, covering deferred features, technical risks, FR refinements, NFR gaps, validation warnings, and process recommendations.

Translates user intent into a precise, unambiguous specification and requirements.

Generates a candid improvement report for a software requirements specification, covering deferred features, technical risks, FR refinement suggestions, NFR gaps, validation warnings, and process recommendations.

Decomposes an approved specification into dependency-aware waves and atomic executable tasks with exact file scope, test-first actions, verification commands, and an execution gate.

Automates the preparation of Easy difficulty diagram specifications from a CSV report and chapter files, generating reports, execution plans, and spec files for MicroSim generation.

Run replication, robustness, and specification-sensitivity workflows for Stata projects. Use when a researcher wants to reproduce a result, rerun a pipeline, compare specifications, audit a do-file sequence, or check whether a claim is stable.

Analyzes a website's current design and user intent to produce a structured redesign specification, including product and design documents, a design system JSON, and a reasoning trace.

Create or update the feature specification from a natural language feature description.

Create or update the feature specification from a natural language feature description.

Takes a PRD, reference URL, screenshot, or keywords to produce a DESIGN.md specification, then generates production-ready web code that meets UI/UX, visual, motion, and responsive standards.

Convert narrative technical documents into grounded Mathematical Problem Specifications with variables, constraints, objectives, and uncertainty.

Generates client SDKs in TypeScript, Python, Go, and Java from OpenAPI specifications

Design technical architecture, select technology stack, and define implementation strategy from specifications and constitution constraints.

Validate Claude Code skills against the agentskills specification. Catches structural, semantic, and naming issues before users do.

Feature specification creation from codebase research. Produces requirements, acceptance criteria, architecture decisions, implementation plans, and risk analysis.

Prepare bid packages with specifications and requirements. TRIGGERS - Use when user needs help with bid-package related tasks.

Prepare bid packages with specifications and requirements. TRIGGERS - Use when user needs help with bid-package related tasks.

OpenAPI/Swagger documentation agent for creating and maintaining comprehensive API specifications with schemas, examples, and security definitions

Create and improve agent skills following the Agent Skills specification. Use when asked to create, write, or update skills.

Run a structured discovery session to build an Allium specification through conversation. Use when the user wants to create a new spec from scratch, elicit or gather requirements, capture domain behaviour, specify a feature or system, define what a system should do, or is describing functionality and needs help shaping it into a specification.

Guides collaborative dialogue to turn ideas into approved designs and specs before any implementation begins.

Writes Behavior-Driven Development scenarios using Gherkin syntax to create executable specifications and test behavior.

Transform an approved video script into a Remotion build specification with scaffolded project directory, compositions, scene components, and render config

Create an llms.txt file from scratch based on repository structure following the llms.txt specification at https://llmstxt.org/

6-phase iterative specification execution workflow covering implementation, testing, review, improvement, commit, and progress tracking with quality-gated convergence.

Guides collaborative dialogue to turn ideas into fully formed designs and specs before any implementation begins.

Generate standardized commit messages following the Conventional Commits specification using a structured XML format.

Create an llms.txt file from scratch based on repository structure following the llms.txt specification at https://llmstxt.org/

Generate structured, machine-readable implementation plans for features, refactoring, upgrades, or infrastructure changes.

Shape a rough product or project idea into a scoped brief before customer discovery, market research, specifications, UX, UI, or implementation planning

Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.

Create or update a MoonSpec feature specification from a natural language feature request or referenced declarative design. Use when the user asks to run or reproduce `/moonspec.specify`, create a `spec.md`, initialize a feature directory under `specs/`, preserve the original feature request for later verification, map source design requirements, or generate a single-story MoonSpec specification with a requirements quality checklist.

Write the executable feature specification — the WHAT and WHY artifact that agents and reviewers treat as source of truth. Owns both /specify and /clarify modes. Load when the user asks to write a feature spec, write a specification, write an executable spec, define functional requirements, capture acceptance criteria as Given/When/Then, or when the spec-driven-development orchestrator routes here. Also triggers on "feature spec", "executable spec", "/specify", "/clarify", "write the spec for this feature", "specification for", "spec-driven", "machine-readable spec". Output: docs/specs/YYYY-MM-DD-<slug>-feature-spec.md. Hard gate: cannot Approve while [NEEDS CLARIFICATION] markers remain.