scapia-oss
Official@scapia-oss
Scapia-oss publishes Kiro skills for spec-driven development: EARS requirements, HLD/LLD design, TDD implementation, validation gates, and multi-repo spec linkage.
Agent Skills by scapia-oss
Showing 24 vetted skills indexed across 1 GitHub repositories.
scapia-osskiro-spec-status
Reports specification progress, pending work, and the next workflow command for Kiro specs.
scapia-osskiro-spec-quick
Generates right-sized spec documents by classifying changes into minimal or standard pipelines.
scapia-osskiro-impl
Implements approved spec tasks using TDD with subagent dispatch and verification gates.
scapia-osskiro-doctor
Diagnose kiro plugin setup and report repo wiring, environment, and hook configuration issues.
scapia-osskiro-next
Reports current spec workflow position and the exact next Kiro command.
scapia-osskiro-validate-gap
Analyzes the gap between feature requirements and the existing codebase to inform design decisions.
scapia-osskiro-impl-fast
Implements low-risk spec tasks sequentially with a single end-of-run build, test, and review gate.
scapia-osskiro-spec-tasks
Generates milestone-based implementation task lists from approved requirements and design documents.
scapia-osskiro-spec-design
Generate technical design documents translating approved requirements into architecture and component boundaries.
scapia-osskiro-spec-init
Initialize spec-driven development specifications through guided triage and workflow selection.
scapia-osskiro-retrospective
Generates evidence-backed session feedback and skill-improvement reports from kiro workflow sessions.
scapia-osskiro-spec-design-hld
Generate high-level architecture design documents for approved feature specifications.
scapia-osskiro-verify-completion
Validates task, fix, test, and feature completion claims against fresh command evidence.
scapia-osskiro-spec-requirements
Generate EARS-format requirements documents from project descriptions and steering context.
scapia-osskiro-spec-design-lld
Generate low-level design documents with interfaces, data models, and contracts from approved high-level designs.
scapia-osskiro-validate-design
Reviews technical design documents against codebase evidence and issues a GO/NO-GO decision.
scapia-osskiro-discovery
Routes new work ideas to the correct spec workflow through structured critique dialogue.
scapia-osskiro-steering-custom
Create custom steering documents capturing domain-specific project patterns and conventions.
scapia-osskiro-debug
Diagnose implementation failures through root-cause-first investigation and structured debug reports.
scapia-osskiro-review
Review task implementations against approved specs, boundaries, and verification evidence.
scapia-osskiro-validate-impl
Validates feature-level integration across completed tasks with test suites, coverage, and design alignment checks.
scapia-osskiro-steering
Generate and sync steering documents that capture project patterns as persistent memory.
scapia-osskiro-spec-batch
Generates complete specs for all roadmap features using parallel subagent dispatch by dependency wave.
scapia-osskiro-spec-link
Creates a cross-repo spec pointer linking this repository to a spec owned by another repository.
Frequently Asked Questions About scapia-oss
FAQPage SchemaWhat tasks can I accomplish with scapia-oss's Kiro skills?▼
You can run the full spec-driven development lifecycle: initialize specs, generate EARS requirements, produce HLD/LLD designs, create task lists, implement with TDD via subagent dispatch, review implementations, validate integration, debug failures, and run retrospectives. Navigation skills show status and the next command.
Who should use the Kiro skill collection?▼
Software engineers and teams practicing spec-driven development, especially those working in multi-repo setups or with slow Gradle builds. kiro-doctor targets plugin consumers verifying their setup, while kiro-retrospective produces improvement backlogs for framework maintainers.
How do I get started with a new feature using these skills?▼
Start with kiro-discovery to determine the right action path, or kiro-spec-init to initialize a specification. kiro-spec-quick adaptively generates a minimal or standard spec based on change risk, then flows into kiro-impl-fast or kiro-impl for implementation.
What prerequisites and dependencies do the Kiro skills require?▼
A correctly wired .kiro/ directory layout with steering documents, a sane Node environment, and the installed plugin with hooks and scripts. kiro-doctor verifies repo wiring, environment sanity, and reports installed plugin components when commands are not firing.
How do the skills handle multi-repo projects?▼
kiro-spec-link creates a pointer from a satellite or peer repo to the spec owning a change in another repo, writing only spec-link.md and a minimal spec.json locally without duplicating content or writing into the other repo. Shared multi-repo-linkage rules govern the behavior.