Search Results for "spec-driven-development" | AgentCC

agent-definition-creation

Use this skill when creating or refining Claude Code sub-agent definitions. Helps design specialized AI assistants with proper YAML frontmatter, system prompts, tool access, and example-driven descriptions. Automatically invoked when user requests "create an agent", "design a sub-agent", "make a specialist", or mentions agent development. Ensures agents follow Anthropic best practices with focused responsibilities, discovery-optimized descriptions, and proper tool restrictions.

SDD Methodology

Use when explaining or applying Spec-Driven Development workflow, guiding through SDD phases, or helping with workflow decisions. Invoked for methodology guidance, workflow optimization, and best practices.

Subagent-Driven Development

Sequential subagent execution with two-stage review gates for implementation plans. Use when executing multi-task plans in the current session, when tasks need fresh subagent context to avoid cross-task pollution, when formal review cycles (spec compliance then code quality) are required between tasks, or when you need diff-based validation of each task before proceeding.

product-spec-kit

Comprehensive skill for Product Managers to create organize and manage Product Teams, Strategy, PRDs, release plans, user stories, and standalone issues with high-quality acceptance criteria. Supports both full documentation workflows (PRD → Plan → Stories) and quick issue creation (standalone stories, tasks, bugs). All documentation follows design-driven development principles with functional, testable acceptance criteria based on visual designs and user flows.

Apex Spec Workflow

moshehbenavraham

This skill should be used when the user asks about "spec system", "session workflow", "createprd", "plansession", "implement session", "validate session", "phase build", "session scope", "task checklist", or when working in a project containing .spec_system/ directory. Provides guidance for specification-driven AI development workflows.

musubix-sdd-workflow

Guide for MUSUBIX SDD (Specification-Driven Development) workflow. Use this when asked to develop features using MUSUBIX methodology, create requirements, designs, or implement code following the 9 constitutional articles.

project-init

Use this skill when starting a new project or adding AgenticDev to an existing project. Scaffolds the directory structure (docs/specs, docs/changes) and configuration files needed for the spec-driven development workflow.

tdd-guide

Test-Driven Development specialist enforcing write-tests-first methodology. Use PROACTIVELY when writing new features, fixing bugs, or refactoring code. Ensures 80%+ test coverage.

Spec Authoring

Use this skill to propose changes via the Spec PR process. It uses the Gemini CLI to generate high-quality draft specifications and to analyze PR feedback, accelerating the spec-driven development workflow. Triggers include "create spec" or "propose change".

Spec Kit Workflow

Guides a specification-driven development workflow. Automatically invoked when discussing new features, specifications, technical planning, or implementation tasks. Ensures proper workflow phases (specify → clarify → plan → checklist → tasks → analyze → implement).

Spec-Driven Development (SDD)

Spec-Driven Development (SDD): a structured workflow (Requirement -> Analysis -> Implementation) that enforces explicit documentation before coding.

spec-driven-dev

Write specifications before code — the agent creates detailed technical specs, validates them, then implements. Use when someone asks to "write a spec first", "plan before coding", "create a technical design document", "spec-driven development", "Kiro-style development", "validate my idea before building", "write an RFC", or "create an architecture doc before implementation". Covers requirement extraction, technical spec templates, validation checklists, implementation plans, and spec-to-code workflows.

spec-driven-dev

Spec-driven development framework with iterative refinement. Orchestrates feature development from intent to implementation via structured specs and task breakdown. Triggers on "/spec.plan", "/spec.refine", "/spec.clarify", "/spec.tasks", "/spec.run", "I want to build", "I want to add", "create spec", "spec-driven", "feature spec".

doc-flow

AI-Driven Specification-Driven Development (SDD) workflow orchestrator - guides skill selection and general SDD methodology

sdd-workflowlayer-0-artifactshared-architecture+2

spec-plan

When the user intends to perform spec-driven development (Spec-first / Spec-driven development), you MUST use this Skill: first converge requirements and constraints into a single actionable, reviewable spec before proceeding to implementation. This Skill ultimately generates exactly one spec file written to /docs/specs/ and performs one git commit (committing only that spec). This Skill does not write implementation code.

speckit

Spec-driven development workflow (Speckit) for generating and maintaining specs, decisions, plans, tasks, and implementation guidance in repos that use specs/###-feature directories.

spec-driver

SPEC-Driven Development workflow for transforming ideas into implementations through Requirements → Design → Tasks phases. Inspired by Kiro IDE's spec-driven approach. Use when: (1) starting a new feature with 'help me with requirements', 'design this', 'spec', 'design', 'requirements', (2) creating technical specifications, (3) breaking down features into tasks, (4) reviewing or updating existing specs. Triggers: requirements analysis, technical design, task breakdown, spec workflow, feature design, I want to build.

openspec-proposal-creation-cn

Create structured change proposals and specification deltas using an OpenSpec-driven approach. Used for planning features, creating proposals, drafting specifications, introducing new capabilities, or initiating development workflows. Trigger phrases include "openspec proposal", "plan", "create proposal", "plan change", "spec feature", "new feature", "new capability", "new requirement", "add feature planning", "design spec".

sdd-update

Progress tracking for spec-driven development. Use to update task status, track progress, journal decisions, move specs between folders, and maintain spec files. Handles the administrative/clerical aspects of specification documents during development.

writing-specification-driven-development

huynhbaoking112

Write specification documents for features using specification-driven development practices, including requirements with user stories, architecture design documents with correctness properties, and implementation plans with task breakdowns. Use when planning a new feature, designing system architecture, creating implementation roadmaps, or documenting technical specifications.

claudecraft

Spec-driven development workflow skill. Auto-loads when working on: - Specification creation or editing - Technical planning - Task decomposition - Implementation within ClaudeCraft context

sdlc-develop

Orchestrates a six-phase SDLC pipeline (discovery, requirements, architecture, workstreams, implementation, summary) to guide feature development. Use when the user runs the /core:develop command, requests spec-driven development, wants to create implementation plans with architecture decisions, or mentions "SDLC", "spec-driven", "plan feature", or "development pipeline". Supports plan persistence, wave-based resume, autonomous mode, and architecture/implementation verification.

arm-cortex-expert

agent-skills-hub

Senior embedded software engineer specializing in firmware and driver development for ARM Cortex-M microcontrollers (Teensy, STM32, nRF52, SAMD). Decades of experience writing reliable, optimized, and maintainable embedded code with deep expertise in memory barriers, DMA/cache coherency, interrupt-driven I/O, and peripheral drivers.

tdd-orchestrator

agent-skills-hub

Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.

prompt-engineering-ui

Prompt patterns for consistent UI generation. Covers precise design intent communication, component specification formats, and iterative refinement patterns for LLM-driven UI development.

minecraft-bukkit-pro

agent-skills-hub

Master Minecraft server plugin development with Bukkit, Spigot, and Paper APIs. Specializes in event-driven architecture, command systems, world manipulation, player management, and performance optimization. Use PROACTIVELY for plugin architecture, gameplay mechanics, server-side features, or cross-version compatibility.

project-mgmt

Spec-driven development with persistent markdown planning. Use when: complex tasks (>5 tool calls), multi-step work, GitHub issues, research tasks, building projects. Creates plan.md, spec.md, findings.md, progress.md in .project/{issue#}/ directory.

aiworkflow-requirements

System specification management skill for AIWorkflowOrchestrator. Search, reference, and update the canonical specifications under `references/`. Assuming specification-driven development, read the minimal necessary documents progressively using resource-map, topic-map, and keywords. Used for: requirements verification, architecture decisions, API/IPC contract verification, security/test policy checks, reflecting specification diffs, registering unassigned tasks, and capturing lessons learned. Typical keywords: specification/requirements/design/API/IPC/type definitions/permissions/history/retry/state management/Zustand/authentication/session/UI/tests/coverage/components/accessibility/deployment. The purpose is to maintain alignment between implementation and specification, prevent missed updates, and convert recurrence-prevention insights into organizational assets. Anchors: • Specification-driven development / Application: canonical-spec synchronization / Purpose: maintain implementation-spec alignment • Progressive disclosure / Application: start reading from resource-map / Purpose: prevent omissions by referencing only the minimum necessary Trigger: specification review, specification update, task-workflow sync, UI specification reflection, IPC contract verification, security requirement review, registering unassigned tasks, syncing lessons-learned

tdd

Test-Driven Development (TDD) best practices for pko-tools repository. Use this skill when implementing new features, fixing bugs, or refactoring code in either the Rust backend (src-tauri/) or TypeScript/React frontend (src/). Specifically use when (1) adding new functionality that needs tests, (2) writing tests before implementation (red-green-refactor), (3) debugging failing tests, (4) improving test coverage, or (5) setting up test infrastructure.

spec

Interview-driven specification development. Use when starting a new project, after context compaction, when SPEC.md is missing or stale, or when the user needs to clarify project architecture. Triggers on "spec", "interview me", "what are we building", or when substantial work is requested without clear requirements.

subagent-driven-development

3-role pipeline (Implementer -> Spec Reviewer -> Quality Reviewer) for plan-driven multi-task implementation. Supports subagent dispatch (Agent tool) and Agent Teams (TeamCreate). Use when a plan file exists in docs/plans/ and work spans 3+ tasks.

spec-driven-development

Spec-Driven Development (SDD) workflow and state management. Use when guiding or executing SDD flows; selecting lanes (full/vibe/bug), managing artifacts, running task progression commands, and keeping change state current through ae sdd CLI.

subagent-driven-development

Sequential subagent execution with two-stage review gates for implementation plans. Use when executing multi-task plans in current session, when tasks need fresh subagent context to avoid pollution, when formal review cycles (spec compliance then code quality) are required between tasks, or when you need diff-based validation of each task before proceeding.

kiro-spec-driven-development

This skill should be used when the user asks to "create a spec", "plan a feature before coding", "write requirements", "design before implementing", "spec-driven development", "break down a feature into tasks", "create a design document", or wants to follow a structured requirements-to-design-to-tasks workflow before writing code. Also triggered by mentions of Kiro methodology or iterative spec refinement.

speckit

organvm-iv-taxis

Specification-Driven Development (SDD) toolkit. Transforms ideas into executable specifications, implementation plans, and task lists. Use for feature planning, PRD creation, or when user invokes /speckit.specify, /speckit.plan, /speckit.tasks commands.

sdd

Service-Driven Development workflow for Effect-TS. Schema-first, type-driven, property-tested. USE THIS SKILL WHEN: - Designing a new feature spanning 3+ services - Sketching service boundaries before implementation - User says "design", "sketch", "SDD", "service-driven" - Planning multi-service composition NOT FOR: single-service CRUD, implementing against an existing spec TRIGGERS ON: "design services", "sketch services", "SDD", "service-driven", "type-driven design", "design the API first", "audit services", "bring to SDD standard", "SDD audit"

sdd-engineer

Spec-Driven Development workflow for AI agents with requirements capture, technical specification, planning, task decomposition, tested implementation, and validation artifacts. Use for multi-step software changes that need traceability, approvals, or rigorous testing; use /sdd-quick for small, low-risk changes.

test-with-examples

For example-driven development: test cases as specifications, input/output pairs, documentation through examples.

clojure-programmer

Clojure-specific philosophy, idioms, and judgment frameworks. Use when working with Clojure code. Emphasizes data-oriented design, runtime validation with spec, REPL-driven development, and the philosophy of simplicity over ease.

sdd-v

Spec-driven development with built-in verification. Plans features (requirements, design, tasks), establishes CLI control surfaces for agent observability, and executes with preflight checks and self-verification loops. Use when planning features, setting up agent control surfaces, executing tasks, or when the user mentions spec, plan, design, execute, go, preflight, or control surface.

spec-driven-development

Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.

minecraft-bukkit-pro

Master Minecraft server plugin development with the Bukkit, Spigot, and Paper APIs. Specializes in event-driven architecture, command systems, world manipulation, player management, and performance optimization. Use PROACTIVELY for plugin architecture, gameplay mechanics, server-side features, or cross-version compatibility.

ladder-init

Initializes Ladder project structure with OVERVIEW.md and progress tracking. Use when starting phased spec-driven development or when the user says "ladder init."

spec-driven-dev

Specification-driven development with structured requirements, planning workflows, task breakdown, and quality gates. Covers product briefs, PRDs, technical specs, and implementation plans.

sdd-workflow

Use this skill when designing new features, pages, or systems before writing code. Enforces v100 Specification-Driven Development with exhaustive UI/UX design (12+ states, 6 breakpoints, dark mode, RTL, motion, i18n), API contracts, data models, event architecture, observability, and acceptance criteria.

tdd-orchestrator

Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.

auto-coder

Autonomous spec-driven development agent. Reads DEV_SPEC.md, identifies next task, implements code, runs tests, and persists progress — all in one command with minimal user intervention. Use when user says "auto code", "自动开发", "自动写代码", "auto dev", "一键开发", "autopilot", or wants fully automated spec-to-code workflow. Replaces manual dev-workflow pipeline with autonomous execution.

arm-cortex-expert

Senior embedded software engineer specializing in firmware and driver development for ARM Cortex-M microcontrollers (Teensy, STM32, nRF52, SAMD). Decades of experience writing reliable, optimized, and maintainable embedded code with deep expertise in memory barriers, DMA/cache coherency, interrupt-driven I/O, and peripheral drivers.