ragarciaruben 1.20.19 → 1.20.21

package/{.github/copilot-context/prompts/sync-instructions.prompt.md → get-shit-done/templates/opencode/commands/sync-instructions.md}

@@ -1,15 +1,11 @@
 ---
-name: sync-instructions
-description: Regenerate .github/copilot-instructions.md from .planning/ source documents — keeps the always-on context digest up to date
-mode: agent
-tools:
-  - editFiles
-  - search
+description: Regenerate AGENTS.md from .planning/ source documents — keeps the always-on context digest up to date
+agent: executor
 ---
 
 # Sync Instructions
 
-Regenerate `.github/copilot-instructions.md` from the current state of `.planning/` documents. Run this after significant changes to PROJECT.md, STATE.md, or ROADMAP.md.
+Regenerate `AGENTS.md` from the current state of `.planning/` documents. Run this after significant changes to PROJECT.md, STATE.md, or ROADMAP.md.
 
 ## Step 1: Read Source Documents
 
@@ -29,12 +25,12 @@ From the documents, extract:
 5. **Active constraints** — from PROJECT.md Constraints (pick top 3-4 most impactful)
 6. **Recent key decisions** — from PROJECT.md Key Decisions (last 3-4 entries, most recent first)
 
-## Step 3: Rewrite copilot-instructions.md
+## Step 3: Rewrite AGENTS.md
 
-Overwrite `.github/copilot-instructions.md` with a fresh version. Keep it **under 100 lines**. Use this structure:
+Overwrite `AGENTS.md` with a fresh version. Keep it **under 100 lines**. Use this structure:
 
 ```markdown
-# Project Copilot Instructions
+# Project Instructions
 
 <!--
   Auto-generated from .planning/ documents.
@@ -66,7 +62,7 @@ Overwrite `.github/copilot-instructions.md` with a fresh version. Keep it **unde
 
 [Keep the reference table — update if new documents were added]
 
-## Quick Commands (run in Copilot Chat)
+## Quick Commands (run in OpenCode)
 
 [Keep the commands table unchanged]
 ```
@@ -75,12 +71,12 @@ Overwrite `.github/copilot-instructions.md` with a fresh version. Keep it **unde
 
 Print:
 ```
-✅ .github/copilot-instructions.md updated
+✅ AGENTS.md updated
 
 Synced from:
   .planning/PROJECT.md    → description, constraints, decisions
   .planning/STATE.md      → current position, last activity
   .planning/ROADMAP.md    → phase count
 
-The updated instructions will be auto-loaded on your next Copilot Chat request.
+The updated instructions will be auto-loaded on your next OpenCode session.
 ```

package/{.github/copilot-context/prompts/sync-jira.prompt.md → get-shit-done/templates/opencode/commands/sync-jira.md}

@@ -1,10 +1,6 @@
 ---
 description: "Pull Jira tickets and sync them into your .planning/ roadmap as phases"
-mode: agent
-tools:
-  - editFiles
-  - search
-  - jira/*
+agent: executor
 ---
 
 # Sync Jira to Roadmap
@@ -16,7 +12,7 @@ Import Jira tickets into `.planning/ROADMAP.md` as actionable phases.
 The user should provide ONE of:
 - A **Jira project key** (e.g., `PROJ`) — fetch all open issues
 - A **sprint name or board** — fetch current sprint issues
-- A **JQL query** — custom filter (e.g., `project = PROJ AND sprint in openSprints() AND assignee = currentUser()`)
+- A **JQL query** — custom filter
 - A **list of ticket IDs** (e.g., `PROJ-101, PROJ-102, PROJ-105`)
 
 If the user provides none, **ask** which project/sprint to pull from.
@@ -25,15 +21,7 @@ If the user provides none, **ask** which project/sprint to pull from.
 
 ### Step 1: Fetch tickets from Jira
 
-Use the appropriate tool based on user input:
-- `mcp_jira_jira_search` with a JQL query for flexible searches
-- `mcp_jira_jira_get_sprint_issues` for a specific sprint
-- `mcp_jira_jira_get_project_issues` for a full project
-- `mcp_jira_jira_get_issue` for individual tickets
-
-For discovering boards and sprints:
-- `mcp_jira_jira_get_agile_boards` → find the board
-- `mcp_jira_jira_get_sprints_from_board` → find active/future sprints
+Use the appropriate Jira MCP tool based on user input.
 
 ### Step 2: Map tickets to phases
 
@@ -68,11 +56,11 @@ Display:
 - How many tickets were fetched
 - How they were grouped into phases
 - The updated roadmap structure
-- Any tickets that were skipped (already in roadmap) or couldn't be mapped
+- Any tickets that were skipped or couldn't be mapped
 
 ## Important
 
 - **Never delete existing phases** — only append or update
-- If a Jira ticket is already represented in the roadmap (by ticket ID), **update it** instead of duplicating
+- If a Jira ticket is already represented in the roadmap, **update it** instead of duplicating
 - Preserve manual phases that don't come from Jira
 - Include the Jira ticket ID in every phase/requirement for traceability

package/{.github/copilot-context/prompts/verify-work.prompt.md → get-shit-done/templates/opencode/commands/verify-work.md}

@@ -1,10 +1,6 @@
 ---
-name: verify-work
 description: Verify that completed work meets requirements — checks implementation against .planning/REQUIREMENTS.md and phase success criteria
-mode: agent
-tools:
-  - runInTerminal
-  - search
+agent: verifier
 ---
 
 # Verify Work
@@ -24,16 +20,9 @@ Read:
 ## Step 2: Run the Test Suite
 
 ```bash
-# Full test suite
 npm test 2>&1
-
-# Coverage report
 npm run test:coverage 2>&1
-
-# TypeScript
 npx tsc --noEmit 2>&1
-
-# Linting
 npm run lint 2>&1
 ```
 
@@ -46,7 +35,6 @@ For every requirement ID listed for this phase in `REQUIREMENTS.md`:
 | Requirement | Description | Verification method | Status |
 |-------------|-------------|---------------------|--------|
 | AUTH-01 | User can sign up | Test `POST /auth/register` returns 201 | ✅ / ❌ |
-| AUTH-02 | Password hashed | Check `users` table never stores plaintext | ✅ / ❌ |
 
 For each requirement:
 1. Check if there are tests covering it
@@ -56,7 +44,7 @@ For each requirement:
 ## Step 4: Check Phase Success Criteria
 
 Read the success criteria from ROADMAP.md for this phase.
-For each criterion — make a call: TRUE or FALSE based on evidence (tests, code inspection, running commands).
+For each criterion — make a call: TRUE or FALSE based on evidence.
 
 ## Step 5: Write Verification Report
 
@@ -66,7 +54,7 @@ Write the report to `.planning/phases/[NN]-[phase-name]/VERIFICATION.md`:
 # Verification Report: Phase [N] — [Phase Name]
 
 **Date:** [date]
-**Verified by:** Copilot agent
+**Verified by:** OpenCode agent
 
 ## Test Results
 - Tests: [N passing] / [M total]
@@ -86,13 +74,9 @@ Write the report to `.planning/phases/[NN]-[phase-name]/VERIFICATION.md`:
 | Criterion | Status | Notes |
 |-----------|--------|-------|
 | [Criterion 1] | ✅ | [Evidence] |
-| [Criterion 2] | ❌ | [What's missing / how to fix] |
 
 ## Overall: [PASS ✅ / FAIL ❌]
 
-[Pass: "All requirements met. Phase [N] is complete."]
-[Fail: "N requirements not met. See gaps below."]
-
 ## Gaps (if any)
 
 ### [Requirement ID] — [Description]
@@ -104,23 +88,11 @@ Write the report to `.planning/phases/[NN]-[phase-name]/VERIFICATION.md`:
 ## Step 6: Update Documents
 
 **If PASS:**
-- Mark requirements as complete in `.planning/REQUIREMENTS.md`: `- [x] **AUTH-01**:`
+- Mark requirements as complete in `.planning/REQUIREMENTS.md`
 - Update `.planning/STATE.md` to show phase verified
 - Move to next phase
 
 **If FAIL:**
 - Add gap closure plans to the phase plan directory
 - Update `.planning/STATE.md` with the gaps as blockers
-- Suggest running `/execute-phase [N] --gaps-only`
-
-## Completion
-
-```
-[PASS ✅ / FAIL ❌] Phase [N] Verification
-
-Requirements: [N]/[M] met
-Tests: [N passing]
-Coverage: [X]%
-
-[PASS message OR list of gaps to close]
-```
+- Suggest running `/execute-phase [N]` to fix gaps

package/get-shit-done/templates/opencode.json

@@ -0,0 +1,15 @@
+{
+  "$schema": "https://opencode.ai/config.json",
+  "model": "anthropic/claude-sonnet-4",
+  "instructions": [
+    ".planning/codebase/ARCHITECTURE.md",
+    ".planning/codebase/STRUCTURE.md",
+    ".planning/codebase/CONVENTIONS.md",
+    ".planning/codebase/TESTING.md",
+    ".planning/codebase/STACK.md",
+    ".planning/codebase/INTEGRATIONS.md",
+    ".planning/codebase/CONCERNS.md"
+  ],
+  "default_agent": "executor",
+  "mcp": {}
+}

package/package.json

@@ -1,36 +1,26 @@
 {
   "name": "ragarciaruben",
-  "version": "1.20.19",
-  "description": "A meta-prompting, context engineering and spec-driven development system for Claude Code, OpenCode, Gemini and Codex by TÂCHES.",
+  "version": "1.20.21",
+  "description": "A context engineering and spec-driven development system for GitHub Copilot and OpenCode by TÂCHES.",
   "bin": {
     "get-shit-done-cc": "bin/install.js"
   },
   "files": [
     "bin",
-    "commands",
     "get-shit-done",
-    "agents",
-    "hooks/dist",
-    "scripts",
-    ".github/copilot-context",
     ".github/copilot-instructions.md",
     ".github/prompts",
     ".github/instructions",
     ".github/agents",
-    ".planning",
-    ".vscode/settings.json"
+    ".planning"
   ],
   "keywords": [
-    "claude",
-    "claude-code",
+    "copilot",
+    "github-copilot",
+    "opencode",
     "ai",
-    "meta-prompting",
     "context-engineering",
-    "spec-driven-development",
-    "gemini",
-    "gemini-cli",
-    "codex",
-    "codex-cli"
+    "spec-driven-development"
   ],
   "author": "TÂCHES",
   "license": "MIT",