User Story
As a Kiro user
I want to use the OpenSpec system and its associated commands/shortcuts
So that I can efficiently create, update, and manage specifications using a consistent, supported workflow.
Description
Kiro users currently lack first-class support for working with OpenSpec, despite OpenSpec being used as a command‑line–driven specification and workflow tool within the broader development ecosystem. OpenSpec is not tied to a specific AI or IDE, but provides a standard CLI interface and extensible flows that can be leveraged by tools and agents. [Guild Meeting | Teams]
This issue proposes enabling Kiro users to:
- Initialise and work with OpenSpec‑managed projects
- Invoke common OpenSpec workflows via well-defined commands or shortcuts
- Align Kiro-based workflows with existing OpenSpec usage patterns
Acceptance Criteria
- Kiro users can initialise an OpenSpec project from within a Kiro workflow or environment
- Core OpenSpec commands (e.g. spec creation, update, sync) are discoverable and usable via documented commands or shortcuts
- Configuration (e.g. project or governance settings) is respected and sourced from standard OpenSpec configuration files
- Usage does not assume a specific IDE and works in CLI-centric workflows
- Documentation exists describing how Kiro integrates with OpenSpec and which commands/shortcuts are supported
Notes / Context
- OpenSpec is used as a standalone CLI tool and can be extended or integrated into other workflows [Guild Meeting | Teams]
- There is precedent for OpenSpec-related commands such as syncing or updating specs from deltas, indicating a clear command model suitable for reuse in Kiro [Ideas for...Challenge | Teams]
- This issue focuses on enablement and integration, not on redefining OpenSpec behaviour itself
User Story
As a Kiro user
I want to use the OpenSpec system and its associated commands/shortcuts
So that I can efficiently create, update, and manage specifications using a consistent, supported workflow.
Description
Kiro users currently lack first-class support for working with OpenSpec, despite OpenSpec being used as a command‑line–driven specification and workflow tool within the broader development ecosystem. OpenSpec is not tied to a specific AI or IDE, but provides a standard CLI interface and extensible flows that can be leveraged by tools and agents. [Guild Meeting | Teams]
This issue proposes enabling Kiro users to:
Acceptance Criteria
Notes / Context