@tudeorangbiasa/sdd-multiagent-opencode 0.2.1 → 0.2.2

package/.opencode/commands/sdd-apply.md

@@ -28,6 +28,13 @@ Implement an existing change from `specs/active/<change-id>/`.
 - Verify with the commands listed in `design.md` when available.
 - Stop on blockers. Do not silently skip tasks.
 
+## Test Integrity
+
+- **Source of Truth**: The "Test Spec" table in `tasks.md` defines the exact test cases. You must implement every row in that table.
+- **No Weakening**: You are FORBIDDEN from modifying test assertions (e.g., changing `toBe(401)` to `toBeTruthy()`, or removing edge cases) to make a test pass.
+- **Fix Implementation, Not Test**: If a test fails, fix the source code (`src/...`), NOT the test code (`*.test.ts`).
+- **Report Mismatches**: If you believe the Test Spec in `tasks.md` is incorrect, STOP and report it as a blocker. Do not silently change the test to fit your implementation.
+
 ## Context Safety
 
 - Treat `tasks.md` and `progress.md` as the source of truth, not chat history.

package/.opencode/commands/sdd-propose.md

@@ -77,6 +77,7 @@ Keep artifacts short enough to review. Prefer concrete bullets over generic proc
 - Dependencies, if any
 - Test or verification step for each phase
 - Suggested execution mode: sequential or parallel-safe groups
+- **Structured Test Specifications**: For tasks involving logic, include a Markdown table with columns: `Scenario`, `Input`, `Expected Output`, `Mock Requirement`. The implementer must translate this table exactly into code.
 
 `progress.md` for large changes must include:
 - Current phase

package/.opencode/commands/sdd-quick.md

@@ -0,0 +1,165 @@
+---
+description: Quick one-shot fix for cosmetic/config changes with lightweight verification
+agent: sdd-implementer
+---
+
+Execute a small, safe change with minimal overhead. No full spec artifacts required.
+
+## Usage
+
+```text
+/sdd-quick "fix typo: succesful -> successful"
+/sdd-quick "rename isLoading to isFetching in auth.ts"
+```
+
+## Phase 1: Rule-Based Change Classification
+
+Do NOT guess the change type. Classify using these deterministic rules, evaluated in order. The first matching rule wins.
+
+### Force → CONTRACT (❌ Abort → suggest `/sdd-propose`)
+- Change to any exported function, class, interface, or type name
+- Change to any file matching: `**/api/**`, `**/dto/**`, `**/schema/**`, `**/types/public-api.ts`, `**/graphql/types.ts`
+- Change to function signature (add/remove/rename parameter)
+- Change to any file explicitly marked as `@public` or `@api` in JSDoc
+
+### Force → LOGIC (❌ Abort → suggest `/sdd-propose`)
+- ANY change to operators: `>`, `<`, `>=`, `<=`, `==`, `===`, `!=`, `!==`, `&&`, `||`, `!`, `?:`
+- ANY change to control flow keywords: `if`, `else`, `switch`, `case`, `for`, `while`, `return`, `throw`, `try`, `catch`, `finally`
+- ANY change to a condition expression or boolean logic
+- ANY change to calculation or math expression
+- Adding or removing a function call
+- Changing a function's return value
+
+### Force → CONFIG (⚠️ Allowed with warning)
+- Change to constant value, env var, feature flag, or config file (`*.config.*`, `.env`, `*.json`)
+- Change to a string that is NOT rendered in a UI component
+
+### Default → COSMETIC (✅ Allowed)
+- Typo fix in string literal or comment
+- Whitespace or formatting change
+- Internal variable rename (not exported)
+- Import reordering or unused import removal
+- Dead code removal
+- Comment addition or update
+
+If the change matches CONTRACT or LOGIC, STOP immediately. Do not proceed. Report why and suggest `/sdd-propose`.
+
+## Phase 2: Pre-Flight Checks
+
+### Lock File Check
+1. Check if `specs/.sdd-lock` exists.
+2. If it exists:
+   - Read the PID from the lock file.
+   - Check if that process is still running (`ps -p <PID>` or equivalent).
+   - If PID is alive → Warn: "Another SDD process is active. Proceed anyway? (yes/no)"
+   - If PID is dead → Remove stale lock and continue.
+3. If no lock exists → Create `specs/.sdd-lock` with current PID and command name.
+
+### Cross-File Impact Scan
+1. Identify the symbol, string, or pattern that will change.
+2. Run a project-wide grep for that pattern.
+3. Count references:
+   - ≤ 5 references → ✅ Continue
+   - > 5 references → ⚠️ Flag as "Ripple Risk", show user the affected files, ask for confirmation before proceeding.
+
+### String Length Check (for string changes only)
+1. Calculate the length delta: `|new_length - old_length|`
+2. Calculate percentage change: `delta / old_length * 100`
+3. If delta > 20 characters OR percentage increase > 50%:
+   - Flag as "UI Layout Risk"
+   - Check if the string is in a UI component file (`.tsx`, `.vue`, `.jsx`, `.svelte`)
+   - If in UI component → Require explicit user confirmation before proceeding
+4. If the string is in a non-UI file (`.ts` logic, config, etc.) → Allow without flag
+
+## Phase 3: Execute Change
+
+- Make the smallest possible change that satisfies the request.
+- Do NOT touch any file beyond what is strictly necessary.
+- Do NOT create new files.
+- Do NOT refactor or "improve" surrounding code.
+- Do NOT change logic, only what was explicitly requested.
+
+## Phase 4: Verification
+
+### Mandatory Checks
+Run the project's available verification commands. Check `package.json` scripts or equivalent:
+
+1. **Lint**: `npm run lint` (or `pnpm lint`, `yarn lint`, etc.)
+2. **Typecheck**: `npm run typecheck` (or `tsc --noEmit`, `vue-tsc`, etc.)
+
+### Decision Table
+| Result | Action |
+|--------|--------|
+| Both pass | ✅ Continue to Phase 5 |
+| Lint fails | ❌ Auto-revert all changes, report failure |
+| Typecheck fails | ❌ Auto-revert all changes, report failure |
+| Test fails (if run) | ⚠️ Check if failure is pre-existing or caused by this change. If caused by this change → auto-revert. If pre-existing → allow with warning. |
+
+If the project has NO lint or typecheck script → ❌ Reject, suggest `/sdd-propose` (project lacks safety net for quick changes).
+
+## Phase 5: Atomic Ledger Append
+
+Do NOT create individual files per change. Append to a single ledger file.
+
+### Ledger File: `specs/QUICKFIX_LOG.md`
+
+Format for each entry:
+
+```markdown
+## YYYY-MM-DD HH:MM — <kebab-case-slug>
+
+- **Trigger:** `/sdd-quick "<original request>"`
+- **Files:** `<file-path>` (L<line>, L<line>)
+- **Type:** Cosmetic | Config
+- **Verification:** `npm run lint` passed, `npm run typecheck` passed
+- **Cross-file refs:** <count> files affected (list if > 3)
+- **Status:** ✅ Applied | ❌ Reverted (reason)
+```
+
+### Atomic Write Procedure
+1. Read current content of `specs/QUICKFIX_LOG.md` (create if not exists, with header `# Quick Change Log`)
+2. Append new entry at the END of the file
+3. Write to temp file: `specs/QUICKFIX_LOG.md.tmp`
+4. Atomic rename: replace `specs/QUICKFIX_LOG.md` with temp file
+5. Remove `specs/.sdd-lock`
+
+### Ledger Maintenance
+If the ledger exceeds 50 entries:
+- Move the oldest 25 entries to `specs/QUICKFIX_LOG_ARCHIVE.md`
+- Keep only the most recent 25 entries in the main ledger
+
+## Anti-Generic Gate
+
+Before final output, verify:
+
+- [ ] Change type was classified using deterministic rules, not AI judgment.
+- [ ] Lock file was checked and cleaned up.
+- [ ] Cross-file scan was performed.
+- [ ] Lint and typecheck were run and passed.
+- [ ] Ledger was updated atomically.
+- [ ] No logic, contract, or new files were touched.
+
+If any item fails, report the failure and do not claim success.
+
+## Output
+
+End with:
+
+```markdown
+changed: Quick fix applied — <slug>
+type: Cosmetic | Config
+verified: lint + typecheck passed
+cross-file refs: <count> files
+
+Log: specs/QUICKFIX_LOG.md
+
+Next: commit the change or run `/sdd-quick` again.
+```
+
+If aborted:
+
+```markdown
+aborted: Quick fix rejected — <slug>
+reason: <specific rule that blocked it>
+suggestion: Run `/sdd-propose "<request>"` for full workflow.
+```

package/.opencode/commands/sdd-ship.md

@@ -21,6 +21,15 @@ Verify a completed change before considering it ready.
 - Do not make product code changes unless the user explicitly asks for fixes.
 - If the user asks to finalize, mark the change complete only when readiness is `yes`.
 
+## Asymmetric Verification
+
+Perform a strict audit comparing the "Test Spec" tables in `tasks.md` against the actual test files (`*.test.ts`):
+
+- **Completeness**: Ensure every row in the Test Spec table has a corresponding test case in the code.
+- **Assertion Strength**: Check for "weakening" (e.g., spec says `expect(status).toBe(401)` but code says `expect(status).toBeGreaterThan(400)`). This is a VIOLATION.
+- **Mock Accuracy**: Verify mocks match the "Mock Requirement" column in the spec.
+- **Halt on Violation**: If you find a violation, DO NOT attempt to auto-correct. Mark `ready: no` and report the specific mismatch in findings.
+
 ## Review Focus
 
 - Requirements satisfied

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tudeorangbiasa/sdd-multiagent-opencode",
-  "version": "0.2.1",
+  "version": "0.2.2",
   "description": "Spec-Driven Development workflow kit for OpenCode with 4 core commands, multi-agent support, and configurable model routing",
   "type": "module",
   "main": ".opencode/plugins/sdd-register.js",