Galileo Labs

User Tools

Site Tools

You are here: start » tips » openspec
tips:openspec

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
tips:openspec [2025/11/08 08:01] – sscipionitips:openspec [2025/11/12 06:30] (current) – [install] sscipioni
Line 9: Line 9:
 </code> </code>
  
 +<code bash | ~/.kilocode/workflows/openspec-refine.md>
 +<!-- OPENSPEC:START -->
 +### Workflow: OpenSpec Refine Change Proposal
 +
 +This workflow is designed to update the detailed specifications (spec deltas) and the implementation task list (tasks.md) within an existing OpenSpec change folder after the main proposal.md has been modified.
 +
 +**Input:**
 +- A valid OpenSpec change ID (e.g., 'add-user-profiles').
 +
 +**Steps:**
 +1. **Analyze Proposal:** Read the contents of the `openspec/changes/<change-id>/proposal.md` file to understand the new or modified requirements.
 +2. **Update Spec Delta:** Using the new requirements from the proposal, carefully modify the spec delta files (located in `openspec/changes/<change-id>/specs/`) to include, modify, or remove requirements and scenarios.
 +3. **Update Tasks:** Review and update the `openspec/changes/<change-id>/tasks.md` file, ensuring the checklist of implementation steps is accurate, complete, and aligned with the newly refined spec delta.
 +4. **Validation (Optional):** After updating, run the `openspec validate <change-id>` command in the terminal to check for any structural errors in the spec deltas. Inform the user of the validation result.
 +5. **Confirmation:** Confirm to the user that the specs and tasks have been successfully refined based on the proposal updates.
 +
 +**Goal:** Synchronize the spec deltas and implementation tasks with the latest version of the change proposal.
 +<!-- OPENSPEC:END -->
 +</code>
 ===== add openspec to existing project ===== ===== add openspec to existing project =====
  
Line 20: Line 39:
 Please read openspec/project.md and help me fill out with details about my project, tech stack, and conventions. Please read openspec/project.md and help me fill out with details about my project, tech stack, and conventions.
 </code> </code>
 +
 +it is possible to change openspec tools with "openspec init" and "openspec update"
  
 ===== add new feature ===== ===== add new feature =====
Line 25: Line 46:
 ==== Proposal ==== ==== Proposal ====
  
 +1) create proposal
 <code bash> <code bash>
 # kilocode # kilocode
Line 51: Line 72:
   * **tasks.md**: Detailed implementation checklist broken into 5 phases (design, configuration, processor modification, main function updates, and testing)   * **tasks.md**: Detailed implementation checklist broken into 5 phases (design, configuration, processor modification, main function updates, and testing)
   * **spec.md**: Specification deltas with both MODIFIED (existing SVM loading requirement) and ADDED (new model configuration requirement) sections, including proper scenarios   * **spec.md**: Specification deltas with both MODIFIED (existing SVM loading requirement) and ADDED (new model configuration requirement) sections, including proper scenarios
 +
 +2) **Review proposal.md** and rebuild spec.md and tasks.md
 +<code>
 +/openspec-refine.md <change-id>
 +</code>
 +
 +3) **Review spec.md and tasks.md**
 +
  
 eventually check status of proposals eventually check status of proposals
Line 85: Line 114:
 openspec archive load-multiple-svm-models --skip-specs --yes openspec archive load-multiple-svm-models --skip-specs --yes
 </code> </code>
 +
  
  
tips/openspec.1762585302.txt.gz · Last modified: by sscipioni

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki