Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By jasonkneen
Implement spec-driven development workflow: convert vague ideas to EARS requirements, generate technical design and steering documents, break designs into sequenced tasks with dependencies, apply QA checklists, AI prompting strategies, and troubleshooting for structured, reliable feature delivery.
npx claudepluginhub jasonkneen/kiro --plugin kiro-spec-drivenCreate comprehensive steering documents for a development project based on the project type and requirements.
Create comprehensive steering documents for a development project based on the project type and requirements.
Effective communication strategies for AI-assisted development. Learn context-first prompting, phased interactions, iterative refinement, and validation techniques to get better results from Claude and other AI coding assistants.
Create comprehensive steering documents for development projects. Generates project-specific standards, git workflows, and technology guidelines in .kiro/steering/ directory.
Transform approved requirements into comprehensive technical designs. Define system architecture, component interactions, data models, and interfaces to create a blueprint for implementation.
Comprehensive testing and validation strategies for spec-driven development. Learn phase-specific validation techniques, quality gates, and testing approaches to ensure high-quality implementation.
Transform vague feature ideas into clear, testable requirements using EARS format. Capture user stories, define acceptance criteria, identify edge cases, and validate completeness before moving to design.
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Specification-Driven Development with Process Discipline for Claude Code
Spec-Driven Development Workflow for Claude Code. A 6-step pipeline: Requirements β Code Analysis β Design β Implement β Verify β Self-Improve. Specifications are the source of truth, code is a verified artifact.
Spec Driven Development toolkit - structured specification, planning, and implementation workflows for systematic feature development
Spec-driven development with search, conflict detection, and reporting
Specification-driven development workflow: specify β plan β tasks β implement
Spec-driven development workflow - transforms ideas into structured specifications (requirements, design, tasks) before implementation.
Collection of Claude Code skills, MCP servers, and hooks for enhanced productivity
Learn from conversation history to improve Claude Code performance. Analyzes logs for communication patterns, model understanding, assumptions, efficiency, and extracts actionable lessons.
A comprehensive guide to systematic feature development using the three-phase spec process: Requirements β Design β Tasks.
New to spec-driven development? β Start with Methodology Overview
Ready to create your first spec? β Jump to Process Guide
Looking for examples? β Browse Examples & Case Studies
Need templates? β Get Ready-to-Use Templates
Working with AI? β Learn Prompting Strategies
π Need detailed navigation? β See Complete Navigation Index - Find content by role, problem, or learning style
Learn the foundational concepts and philosophy behind spec-driven development
Step-by-step walkthrough of the three-phase workflow
Insights into decision-making frameworks and thought processes
Effective communication techniques for AI collaboration
Practical guidance for implementing features from specs
Curated references and learning materials
Real-world case studies and complete spec examples