From 9578366e3655fc92274e3f1b5b08157e34930bf5 Mon Sep 17 00:00:00 2001 From: Summer Shen <3244742300@qq.com> Date: Tue, 31 Mar 2026 09:14:32 +0800 Subject: [PATCH] init repo --- .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 + .gitignore | 10 + .opencode/command/opsx-apply.md | 149 ++ .opencode/command/opsx-archive.md | 154 ++ .opencode/command/opsx-explore.md | 170 ++ .opencode/command/opsx-propose.md | 103 + .../skills/openspec-apply-change/SKILL.md | 156 ++ .../skills/openspec-archive-change/SKILL.md | 114 + .opencode/skills/openspec-explore/SKILL.md | 288 +++ .opencode/skills/openspec-propose/SKILL.md | 110 + .python-version | 1 + README.md | 0 .../changes/add-skill-support/.openspec.yaml | 2 + openspec/changes/add-skill-support/design.md | 147 ++ .../changes/add-skill-support/proposal.md | 31 + .../specs/agent-workflow/spec.md | 45 + .../specs/skill-loader/spec.md | 38 + .../specs/skill-registry/spec.md | 57 + openspec/changes/add-skill-support/tasks.md | 36 + openspec/config.yaml | 20 + pyproject.toml | 21 + src/llama_agent_skills/__init__.py | 77 + src/llama_agent_skills/agent.py | 48 + src/llama_agent_skills/config.py | 34 + src/llama_agent_skills/registry.py | 44 + src/llama_agent_skills/skill.py | 52 + uv.lock | 2049 +++++++++++++++++ 34 files changed, 5200 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 .gitignore create mode 100644 .opencode/command/opsx-apply.md create mode 100644 .opencode/command/opsx-archive.md create mode 100644 .opencode/command/opsx-explore.md create mode 100644 .opencode/command/opsx-propose.md create mode 100644 .opencode/skills/openspec-apply-change/SKILL.md create mode 100644 .opencode/skills/openspec-archive-change/SKILL.md create mode 100644 .opencode/skills/openspec-explore/SKILL.md create mode 100644 .opencode/skills/openspec-propose/SKILL.md create mode 100644 .python-version create mode 100644 README.md create mode 100644 openspec/changes/add-skill-support/.openspec.yaml create mode 100644 openspec/changes/add-skill-support/design.md create mode 100644 openspec/changes/add-skill-support/proposal.md create mode 100644 openspec/changes/add-skill-support/specs/agent-workflow/spec.md create mode 100644 openspec/changes/add-skill-support/specs/skill-loader/spec.md create mode 100644 openspec/changes/add-skill-support/specs/skill-registry/spec.md create mode 100644 openspec/changes/add-skill-support/tasks.md create mode 100644 openspec/config.yaml create mode 100644 pyproject.toml create mode 100644 src/llama_agent_skills/__init__.py create mode 100644 src/llama_agent_skills/agent.py create mode 100644 src/llama_agent_skills/config.py create mode 100644 src/llama_agent_skills/registry.py create mode 100644 src/llama_agent_skills/skill.py create mode 100644 uv.lock diff --git a/.github/prompts/opsx-apply.prompt.md b/.github/prompts/opsx-apply.prompt.md new file mode 100644 index 0000000..494e10e --- /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: + - Context 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 the files listed in `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.