From peterfile-devpilot-agents
Create a Kiro spec for a feature in .kiro/specs create/update feature spec/PRD/RFC—requirements, design doc, and implementation tasks checklist.Trigger on spec/specification/PRD/RFC/tech spec, requirements/user story/acceptance criteria/EARS, design doc/architecture, task breakdown/implementation plan/checklist; 需求/验收/设计/任务.
npx claudepluginhub joshuarweaver/cascade-ai-ml-agents-misc-1 --plugin peterfile-devpilot-agentsThis skill uses the workspace's default tool permissions.
Transform ideas into comprehensive specifications, design documents, and actionable implementation plans.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Transform ideas into comprehensive specifications, design documents, and actionable implementation plans.
Use this skill when you want a Kiro-style spec pack under .kiro/specs/:
Storage: .kiro/specs/{feature-name}/ (kebab-case)
WHEN [event] THEN THE [system] SHALL [response]
IF [condition] THEN THE [system] SHALL [response]
WHILE [state] THE [system] SHALL [response]
### Property N: [Name]
_For any_ [inputs], [precondition], [system] SHALL [behavior].
**Validates: Requirement X.Y**
| Phase | Output File | Key Content |
|---|---|---|
| Requirements | requirements.md | User stories + EARS ACs |
| Design | design.md | Architecture + Interfaces + Properties |
| Tasks | tasks.md | Checkbox task list |
stateDiagram-v2
[*] --> Requirements
Requirements --> ReviewReq : Complete
ReviewReq --> Requirements : Changes
ReviewReq --> Design : Approved
Design --> ReviewDesign : Complete
ReviewDesign --> Design : Changes
ReviewDesign --> Tasks : Approved
Tasks --> ReviewTasks : Complete
ReviewTasks --> Tasks : Changes
ReviewTasks --> [*] : Approved
Execute : Execute Single Task
[*] --> Execute : Task Request
Execute --> [*] : Complete
Determine current state by checking:
# Check for .kiro directory
if [ -d ".kiro/specs" ]; then
# List features
ls .kiro/specs/
# For specific feature, check phase
FEATURE="$1"
if [ -f ".kiro/specs/$FEATURE/requirements.md" ]; then
echo "Requirements exists"
fi
if [ -f ".kiro/specs/$FEATURE/design.md" ]; then
echo "Design exists"
fi
if [ -f ".kiro/specs/$FEATURE/tasks.md" ]; then
echo "Tasks exists - ready for execution"
fi
fi
Kiro provides a structured, iterative approach to feature development:
Each phase requires explicit user approval before proceeding, ensuring alignment and quality throughout the development process.