Results for “spec”

Initialize and manage AC Framework spec-driven workflows using acfm CLI. Use when setting up spec workflows, checking project status, creating changes, or understanding the .acfm/ vs openspec/ directory structures. Essential first step before using any OpenSpec skills.

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

Guides users through the specification-driven development workflow, from requirements gathering through specification, test derivation, implementation, and validation.

Creates detailed, bite-sized implementation plans from specs or requirements, with exact file paths, code, and TDD steps.

Creates detailed, bite-sized implementation plans from specs or requirements, with file structure, task decomposition, and TDD steps.

Creates detailed, bite-sized implementation plans from specs or requirements, with exact file paths, code, and test commands for TDD workflows.

Adopts the voice and methodology of Guy Debord to analyze content through spectacle, détournement, and refusal, offering subversive critiques and creative transformations.

Runs a stateful grilling session that produces workflow specs for workflows the user wants to build. Use when the user says "loop me" or wants workflow specs drawn out of them.

当用户已有确认过的行为规格（理想来自 write-spec），要在编码前把技术问题问清楚、比较方案、锁定技术决策——技术选型、架构、数据模型、接口契约、错误处理、测试策略——并沉淀成可 review 的技术设计依据时使用。不要用于：行为/需求还没钉死（先 write-spec）、想法还模糊（先 refine-idea）、任务拆解或实现计划（那是下游 split-task）、调试或代码评审。

Optimizes agent context setup by structuring rules, specs, source files, error output, and conversation history to improve output quality.

Runs a structured clarifying interview for new project requests before building, then outputs a fully specified prompt.md for a fresh agent session to execute.

Turns a spec or requirements into a detailed, bite-sized implementation plan with exact file paths, code, and test steps for engineers with no codebase context.

Routes engineering design, delivery, reliability, security, operations, and maintenance prompts to a router skill backed by specialist guidance for multiple AI coding agents.

Assign a task to a specific role on your team.

Creates animated flow diagrams from articles, workflow notes, architecture sketches, or process descriptions using a JSON specification and a local Python/Pillow renderer.

Embody the collective voice and methodology of the Russian feminist punk protest group Pussy Riot, using spectacular transgression, collective identity, and punk politics to challenge authoritarian power.

Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.

Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.

Use when specialized expertise is needed to unblock delivery on this task.

Mines SpecStory coding histories from any agent into a persistent corpus, surfaces reproducible workflows with corroborated evidence, and interactively forges chosen ones into skills installed across agent harnesses.

Rereads code, specs, plans, reviews, or skill edits with fresh eyes to catch blunders, oversights, and omissions before closure, reporting concrete evidence-backed findings.

Interactive feature development workflow from idea to implementation. Creates requirements (EARS format), design documents, and implementation task lists. Use when creating feature specs, requirements documents, design documents, or implementation plans. Triggered by "kiro" or references to .kiro/specs/ directory.

Execute the implementation planning workflow using the plan template to generate design artifacts.

Use when deciding which AER-skills sub-skill to use next, before choosing a specialized skill or after a user asks how to sequence manuscript work from topic selection through rebuttal for AER, AER:Insights, or AEJ journals. Routes — does not replace — the specialized skills.

Use when you have a spec or requirements for a multi-step task, before touching code

Use when you have a spec or requirements for a multi-step task, before touching code

Use when you have a spec or requirements for a multi-step task, before touching code

Use when you have a spec or requirements for a multi-step task, before touching code

Use when you have a spec or requirements for a multi-step task, before touching code

Use when you have a spec or requirements for a multi-step task, before touching code