tips:openspec
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| tips:openspec [2025/11/08 08:14] – [Proposal] sscipioni | tips:openspec [2026/03/06 10:26] (current) – sscipioni | ||
|---|---|---|---|
| Line 9: | Line 9: | ||
| </ | </ | ||
| + | <code bash | ~/ | ||
| + | <!-- OPENSPEC: | ||
| + | ### 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., ' | ||
| + | |||
| + | **Steps:** | ||
| + | 1. **Analyze Proposal:** Read the contents of the `openspec/ | ||
| + | 2. **Update Spec Delta:** Using the new requirements from the proposal, carefully modify the spec delta files (located in `openspec/ | ||
| + | 3. **Update Tasks:** Review and update the `openspec/ | ||
| + | 4. **Validation (Optional): | ||
| + | 5. **Confirmation: | ||
| + | |||
| + | **Goal:** Synchronize the spec deltas and implementation tasks with the latest version of the change proposal. | ||
| + | <!-- OPENSPEC: | ||
| + | </ | ||
| ===== add openspec to existing project ===== | ===== add openspec to existing project ===== | ||
| Line 20: | Line 39: | ||
| Please read openspec/ | Please read openspec/ | ||
| </ | </ | ||
| + | |||
| + | it is possible to change openspec tools with " | ||
| ===== add new feature ===== | ===== add new feature ===== | ||
| Line 28: | Line 49: | ||
| <code bash> | <code bash> | ||
| # kilocode | # kilocode | ||
| - | / | + | / |
| - | # other agents | + | # claude and other agents |
| - | /openspec:proposal load multiple svm models | + | /opsx:propose add data lake folder common for python and nextjs backend |
| </ | </ | ||
| Line 37: | Line 58: | ||
| < | < | ||
| openspec/ | openspec/ | ||
| - | └── load-multiple-svm-models | + | -- add-data-lake-folder |
| - | | + | |-- design.md |
| - | | + | |
| - | | + | |-- specs |
| - | | + | | `-- data-lake |
| - | | + | | |
| + | `-- tasks.md | ||
| </ | </ | ||
| Line 54: | Line 77: | ||
| 2) **Review proposal.md** and rebuild spec.md and tasks.md | 2) **Review proposal.md** and rebuild spec.md and tasks.md | ||
| < | < | ||
| - | Can you add acceptance criteria for load multiple svm ? | + | update |
| </ | </ | ||
| Line 77: | Line 100: | ||
| # other agents | # other agents | ||
| - | /openspec: | + | /opsx:apply |
| </ | </ | ||
| Line 93: | Line 116: | ||
| openspec archive load-multiple-svm-models --skip-specs --yes | openspec archive load-multiple-svm-models --skip-specs --yes | ||
| </ | </ | ||
| + | |||
tips/openspec.1762586050.txt.gz · Last modified: by sscipioni
