From 07bf4e33d931cca997c6c59eb46202e55f0fe0df Mon Sep 17 00:00:00 2001 From: Rengesh Date: Tue, 12 May 2026 18:59:21 +0530 Subject: [PATCH] Add OpenSpec framework for unit test enhancement OpenSpec Core Documents: - proposal.md: Problem statement, goals, 7 requirements - design.md: Technical architecture, mock patterns - tasks.md: 56 tasks across 18 phases (P0-P2) - status.md: Progress tracking OpenSpec Specs (11 files): - Module specs: DCM, Queries, Telemetry, Change, Shared, Supporting - Infrastructure: Mock DAO, Database tables, Use cases - Patterns: Test patterns, Module inventory OpenSpec Workflow (.github): - Prompts: explore, propose, apply, archive - Skills: openspec-explore, openspec-propose, openspec-apply-change, openspec-archive-change Key findings: - 3 DAO types: CachedSimpleDao (39 files), SimpleDao (1), ListingDao (1) - 100+ test scenarios documented - 15+ test_utils.go files to create --- .github/prompts/opsx-apply.prompt.md | 149 ++ .github/prompts/opsx-archive.prompt.md | 154 ++ .github/prompts/opsx-explore.prompt.md | 170 +++ .github/prompts/opsx-propose.prompt.md | 103 ++ .github/skills/openspec-apply-change/SKILL.md | 156 ++ .../skills/openspec-archive-change/SKILL.md | 114 ++ .github/skills/openspec-explore/SKILL.md | 288 ++++ .github/skills/openspec-propose/SKILL.md | 110 ++ .../changes/unit-test-enhancement/design.md | 502 +++++++ .../changes/unit-test-enhancement/proposal.md | 334 +++++ .../specs/change-module-spec.md | 246 ++++ .../specs/database-tables-spec.md | 346 +++++ .../specs/dcm-module-spec.md | 459 ++++++ .../specs/mock-infrastructure-spec.md | 441 ++++++ .../specs/module-inventory.md | 333 +++++ .../specs/queries-module-spec.md | 458 ++++++ .../specs/shared-modules-spec.md | 430 ++++++ .../specs/supporting-modules-spec.md | 461 ++++++ .../specs/telemetry-module-spec.md | 323 +++++ .../specs/test-patterns.md | 531 +++++++ .../unit-test-enhancement/specs/use-cases.md | 442 ++++++ .../changes/unit-test-enhancement/status.md | 148 ++ .../changes/unit-test-enhancement/tasks.md | 1269 +++++++++++++++++ openspec/config.yaml | 20 + 24 files changed, 7987 insertions(+) create mode 100644 .github/prompts/opsx-apply.prompt.md create mode 100644 .github/prompts/opsx-archive.prompt.md create mode 100644 .github/prompts/opsx-explore.prompt.md create mode 100644 .github/prompts/opsx-propose.prompt.md create mode 100644 .github/skills/openspec-apply-change/SKILL.md create mode 100644 .github/skills/openspec-archive-change/SKILL.md create mode 100644 .github/skills/openspec-explore/SKILL.md create mode 100644 .github/skills/openspec-propose/SKILL.md create mode 100644 openspec/changes/unit-test-enhancement/design.md create mode 100644 openspec/changes/unit-test-enhancement/proposal.md create mode 100644 openspec/changes/unit-test-enhancement/specs/change-module-spec.md create mode 100644 openspec/changes/unit-test-enhancement/specs/database-tables-spec.md create mode 100644 openspec/changes/unit-test-enhancement/specs/dcm-module-spec.md create mode 100644 openspec/changes/unit-test-enhancement/specs/mock-infrastructure-spec.md create mode 100644 openspec/changes/unit-test-enhancement/specs/module-inventory.md create mode 100644 openspec/changes/unit-test-enhancement/specs/queries-module-spec.md create mode 100644 openspec/changes/unit-test-enhancement/specs/shared-modules-spec.md create mode 100644 openspec/changes/unit-test-enhancement/specs/supporting-modules-spec.md create mode 100644 openspec/changes/unit-test-enhancement/specs/telemetry-module-spec.md create mode 100644 openspec/changes/unit-test-enhancement/specs/test-patterns.md create mode 100644 openspec/changes/unit-test-enhancement/specs/use-cases.md create mode 100644 openspec/changes/unit-test-enhancement/status.md create mode 100644 openspec/changes/unit-test-enhancement/tasks.md create mode 100644 openspec/config.yaml diff --git a/.github/prompts/opsx-apply.prompt.md b/.github/prompts/opsx-apply.prompt.md new file mode 100644 index 0000000..e23ec64 --- /dev/null +++ b/.github/prompts/opsx-apply.prompt.md @@ -0,0 +1,149 @@ +--- +description: Implement tasks from an OpenSpec change (Experimental) +--- + +Implement tasks from an OpenSpec change. + +**Input**: Optionally specify a change name (e.g., `/opsx:apply add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes. + +**Steps** + +1. **Select the change** + + If a name is provided, use it. Otherwise: + - Infer from conversation context if the user mentioned a change + - Auto-select if only one active change exists + - If ambiguous, run `openspec list --json` to get available changes and use the **AskUserQuestion tool** to let the user select + + Always announce: "Using change: " and how to override (e.g., `/opsx:apply `). + +2. **Check status to understand the schema** + ```bash + openspec status --change "" --json + ``` + Parse the JSON to understand: + - `schemaName`: The workflow being used (e.g., "spec-driven") + - Which artifact contains the tasks (typically "tasks" for spec-driven, check status for others) + +3. **Get apply instructions** + + ```bash + openspec instructions apply --change "" --json + ``` + + This returns: + - `contextFiles`: artifact ID -> array of concrete file paths (varies by schema) + - Progress (total, complete, remaining) + - Task list with status + - Dynamic instruction based on current state + + **Handle states:** + - If `state: "blocked"` (missing artifacts): show message, suggest using `/opsx:continue` + - If `state: "all_done"`: congratulate, suggest archive + - Otherwise: proceed to implementation + +4. **Read context files** + + Read every file path listed under `contextFiles` from the apply instructions output. + The files depend on the schema being used: + - **spec-driven**: proposal, specs, design, tasks + - Other schemas: follow the contextFiles from CLI output + +5. **Show current progress** + + Display: + - Schema being used + - Progress: "N/M tasks complete" + - Remaining tasks overview + - Dynamic instruction from CLI + +6. **Implement tasks (loop until done or blocked)** + + For each pending task: + - Show which task is being worked on + - Make the code changes required + - Keep changes minimal and focused + - Mark task complete in the tasks file: `- [ ]` → `- [x]` + - Continue to next task + + **Pause if:** + - Task is unclear → ask for clarification + - Implementation reveals a design issue → suggest updating artifacts + - Error or blocker encountered → report and wait for guidance + - User interrupts + +7. **On completion or pause, show status** + + Display: + - Tasks completed this session + - Overall progress: "N/M tasks complete" + - If all done: suggest archive + - If paused: explain why and wait for guidance + +**Output During Implementation** + +``` +## Implementing: (schema: ) + +Working on task 3/7: +[...implementation happening...] +✓ Task complete + +Working on task 4/7: +[...implementation happening...] +✓ Task complete +``` + +**Output On Completion** + +``` +## Implementation Complete + +**Change:** +**Schema:** +**Progress:** 7/7 tasks complete ✓ + +### Completed This Session +- [x] Task 1 +- [x] Task 2 +... + +All tasks complete! You can archive this change with `/opsx:archive`. +``` + +**Output On Pause (Issue Encountered)** + +``` +## Implementation Paused + +**Change:** +**Schema:** +**Progress:** 4/7 tasks complete + +### Issue Encountered + + +**Options:** +1.