Results for “specification-template”

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

Update an existing specification file for a solution, optimized for Generative AI consumption based on new requirements or code changes.

Author/validate/export Google's DESIGN.md token spec files.

Structures product requirements into a single-page spec with problem, success metrics, scope, user stories, design notes, and rollout plan.

Imported skill _template from vercel

Create performance improvement plan templates. TRIGGERS - Use when user needs help with pip-template related tasks.

Create developer handoff specifications with measurements, behaviors, assets, and edge cases.

Specific description with trigger conditions

phase: 72

Generates customizable prompts for scanning codebases to identify and document high-quality code exemplars, supporting multiple programming languages and configurable analysis depth.

Generates a comprehensive copilot-instructions.md file that guides GitHub Copilot to produce code consistent with project standards, architecture patterns, and exact technology versions by analyzing existing codebase patterns.

Author, lint, diff, and export Google's DESIGN.md design token spec files, including WCAG contrast validation.

Draft product requirements with the problem, users, scope, requirements, metrics, and open decisions.

Author/validate/export Google's DESIGN.md token spec files.

Author/validate/export Google's DESIGN.md token spec files.

Apply consistent method parameter line break formatting across C# projects. Formats parameter lists in declarations (methods, constructors, local functions, delegates) while leaving invocations untouched. Use when the user wants to format method parameters or apply parameter line break formatting.

Create IEP templates for individualized education. TRIGGERS - Use when user needs help with iep-template related tasks.

Create Request for Information templates for construction. TRIGGERS - Use when user needs help with rfi-template related tasks.

Create system-level or epic-level test plans. Use when the user says "lets design test plan" or "I want to create test strategy"

Use when creating a new val and choosing which starter to fork. Covers the catalog of official starter templates, which project shape each one fits, and when forking an existing val is the better starting point.

Generates a single-frame HTML template with a cinematic film-leak aesthetic: warm light leaks, 35mm grain, 2.39:1 letterbox, and serif typography for opening titles or chapter cards.

WelineFramework SystemConfig scope configuration guide. Use when developing, reading, or changing module configuration, scope-aware settings, SystemConfig backend UI, PHTML config templates, w_query('system_config', ...), theme layout configuration entries, or website/store/global config behavior.

ateam-spec

Develop OpenFeature SDK implementations from the specification. Use when implementing the OpenFeature spec in a new language, extending existing SDKs with new features, building custom providers, or contributing to official SDK repositories.

Create Request for Information templates for construction. TRIGGERS - Use when user needs help with rfi-template related tasks.

Create performance improvement plan templates. TRIGGERS - Use when user needs help with pip-template related tasks.

Atomic-design guidance for Templates — page-level wireframes that arrange organisms into layout slots (hero/main/sidebar/footer) without fetching data. Use when authoring components under ui/templates, defining reusable page skeletons, or keeping layout decisions out of pages and organisms.

Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.

Update an existing implementation plan file with new or updated requirements for features, refactoring, package upgrades, design, architecture, or infrastructure.

Clarify requirements before implementing by asking targeted questions when a request has multiple plausible interpretations or key details are unclear.