mirror of
https://github.com/Fission-AI/OpenSpec.git
synced 2026-09-14 20:16:53 +08:00
Tabish Bidiwale
ed924ffcff
- Add `openspec schemas` CLI command with `--json` option for agents - Add `listSchemasWithInfo()` helper to get schema metadata (name, description, artifacts) - Update `openspec-new-change` skill to prompt for schema selection - Update `openspec-continue-change` skill to read schema dynamically from status - Update `openspec-apply-change` skill to use schema-specific context files - Update all slash commands (/opsx:new, /opsx:continue, /opsx:apply) to be schema-agnostic - Add documentation for when to use each schema (spec-driven vs tdd) Agents can now create changes with different workflow schemas and the skills dynamically adapt based on the selected schema's artifact sequence.
33 lines
1.3 KiB
Markdown
33 lines
1.3 KiB
Markdown
## Prerequisites
|
|
|
|
- [x] 0.1 Implement `add-per-change-schema-metadata` change first
|
|
|
|
## 1. Schema Discovery
|
|
|
|
- [x] 1.1 Add CLI command or helper to list schemas with descriptions (for agent use)
|
|
- [x] 1.2 Ensure `openspec templates --schema <name>` returns artifact list for any schema
|
|
|
|
## 2. Update New Change Skill
|
|
|
|
- [x] 2.1 Add schema selection prompt using AskUserQuestion tool
|
|
- [x] 2.2 Present available schemas with descriptions (spec-driven, tdd, etc.)
|
|
- [x] 2.3 Pass selected schema to `openspec new change --schema <name>`
|
|
- [x] 2.4 Update output to show which schema/workflow was selected
|
|
|
|
## 3. Update Continue Change Skill
|
|
|
|
- [x] 3.1 Remove hardcoded artifact references (proposal, specs, design, tasks)
|
|
- [x] 3.2 Read artifact list dynamically from `openspec status --json`
|
|
- [x] 3.3 Adjust artifact creation guidelines to be schema-agnostic
|
|
- [x] 3.4 Handle schema-specific artifact types (e.g., TDD's `tests` artifact)
|
|
|
|
## 4. Update Apply Change Skill
|
|
|
|
- [x] 4.1 Make task detection work with different schema structures
|
|
- [x] 4.2 Adjust context file reading for schema-specific artifacts
|
|
|
|
## 5. Documentation
|
|
|
|
- [x] 5.1 Add schema descriptions to help text or skill instructions
|
|
- [x] 5.2 Document when to use each schema (TDD for bug fixes, spec-driven for features, etc.)
|