@boyingliu01/xp-gate 0.7.0 → 0.8.0

package/skills/sprint-flow/references/qoder-adaptation.md

@@ -1,173 +0,0 @@
-# Qoder Platform Adaptation Guide for Sprint Flow
-
-**Version:** v0.6.0  
-**Platform:** Qoder IDE  
-**Status:** Active
-
----
-
-## 1. Platform Differences
-
-### 1.1 No File-System Event Hooks
-
-| Capability | Claude Code | OpenCode | Qoder |
-|-----------|------------|----------|-------|
-| PreToolUse Hook | ✅ `delphi-review-guard.sh` | ❌ | ❌ |
-| PostToolUse Hook | ✅ `xp-gate-check` | ❌ | ❌ |
-| Custom Tools | ❌ | ✅ `tool()` | ❌ (MCP instead) |
-
-**Adaptation**: Gates embedded in SKILL.md as `<MANDATORY>` instructions. Orchestrator MUST execute checks before each file edit.
-
-### 1.2 No `task()` Subagent API
-
-| Capability | OpenCode | Qoder |
-|-----------|----------|-------|
-| Subagent dispatch | `task(category, load_skills)` | Agent tool (Browser/CodeReview/plan-agent) |
-| Multi-model | Agent config with different models | Qoder multi-model capability |
-| Context isolation | Automatic per-task | Automatic per-Agent |
-
-**Adaptation**: Phase→Agent mapping table in sprint-flow SKILL.md.
-
-### 1.3 No superpowers/gstack Ecosystem
-
-Qoder does not have access to the superpowers or gstack skill ecosystems. All external skill calls are replaced by:
-- **Orchestrator inline execution** (for simple tasks)
-- **Qoder native capabilities** (Memory, CodeReview, browser-use)
-- **Agent subagents** (for complex analysis/planning)
-
----
-
-## 2. External Skill Replacement Matrix
-
-### 2.1 brainstorming (superpowers) → Orchestrator Inline
-
-**Original**: `task(category="deep", load_skills=["brainstorming"])`
-
-**Qoder Replacement**: Orchestrator conducts an interactive requirements exploration dialogue:
-1. Ask clarifying questions about the feature
-2. Analyze existing codebase for relevant modules
-3. Generate a structured design document
-4. Present to user for approval (HARD-GATE)
-
-### 2.2 autoplan (gstack) → plan-agent Subagent
-
-**Original**: `task(category="deep", load_skills=["autoplan"])`
-
-**Qoder Replacement**: Dispatch `plan-agent` subagent with:
-- Design document as input
-- Codebase structure analysis
-- Generate implementation plan with REQ/AC structure
-- Output: specification.yaml draft
-
-### 2.3 freeze/unfreeze (gstack) → Pre-Edit Gate
-
-**Original**: `freeze` locks test directories, `unfreeze` unlocks
-
-**Qoder Replacement**: Pre-Edit Gate in sprint-flow SKILL.md:
-- During Phase 2 freeze state, orchestrator MUST check target file path
-- If file is in test directory → BLOCK with message
-- This is a behavioral constraint, not a physical lock
-
-### 2.4 requesting-code-review (superpowers) → CodeReview Subagent
-
-**Original**: `task(category="unspecified-high", load_skills=["requesting-code-review"])`
-
-**Qoder Replacement**: Dispatch `CodeReview` subagent:
-- Input: changed files since last REQ commit
-- Blind review (no access to business intent, only code)
-- Output: review findings
-
-### 2.5 verification-before-completion (superpowers) → Orchestrator Inline
-
-**Original**: `task(load_skills=["verification-before-completion"])`
-
-**Qoder Replacement**: Orchestrator executes sequentially:
-1. `npm test` / `pytest` / `go test` (test runner)
-2. `npx eslint` / `ruff check` / `golangci-lint` (linter)
-3. `npx tsx src/principles/index.ts` (principles check)
-4. Coverage report check (≥80%)
-
-### 2.6 learn/retro (gstack) → Qoder Memory System
-
-**Original**: `task(load_skills=["learn", "retro"])`
-
-**Qoder Replacement**: 
-- **learn**: `UpdateMemory` with appropriate category
-  - Architecture decisions → `expert_experience`
-  - Coding patterns → `development_practice_specification`
-  - Project structure → `project_introduction`
-- **retro**: `plan-agent` subagent analyzes git log + code quality trends
-  - Output stored via `UpdateMemory` as `task_summary_experience`
-
-### 2.7 browse (gstack) → browser-use MCP
-
-**Original**: `browse` navigates to localhost, interacts with UI
-
-**Qoder Replacement**: Use `browser-use` MCP tools:
-- `navigate_page` → navigate to localhost:3000
-- `click` / `fill` → interact with UI elements
-- `take_screenshot` → capture visual verification
-- `take_snapshot` → get accessibility tree for validation
-
-### 2.8 ship/finishing-branch → Orchestrator Git/GH CLI
-
-**Original**: External skill calls
-
-**Qoder Replacement**: Orchestrator executes:
-- `git add` + `git commit` + `git push`
-- `gh pr create` + `gh pr merge`
-- Standard git workflow (platform-independent)
-
----
-
-## 3. genui Widget Integration
-
-### 3.1 Quality Report Widget
-
-**Trigger**: After Phase 3 REVIEW completes
-
-**Execution**:
-```
-show_widget(widget_path="plugins/qoder/widgets/quality-report.html", data={...quality-report.json contents...})
-```
-
-### 3.2 Sprint Dashboard Widget
-
-**Trigger**: User requests `/sprint-status` or Phase transition
-
-**Execution**:
-```
-show_widget(widget_path="plugins/qoder/widgets/sprint-dashboard.html", data={...sprint-state.json contents...})
-```
-
----
-
-## 4. Memory System Integration
-
-### 4.1 Learnings Categories
-
-| ralph-loop Category | Qoder Memory Category | Scope |
-|--------------------|-----------------------|-------|
-| permanent (architecture) | `expert_experience` | workspace |
-| permanent (convention) | `development_practice_specification` | workspace |
-| permanent (structure) | `project_introduction` | workspace |
-| contextual | Not persisted | session only |
-| sprint retro | `task_summary_experience` | workspace |
-
-### 4.2 Memory Lifecycle
-
-1. **REQ complete** → `UpdateMemory` for permanent learnings
-2. **Sprint Phase 5** → `UpdateMemory` for sprint-level retro
-3. **Next sprint** → `SearchMemory` to recall relevant learnings
-4. **Stale learnings** → User can request memory cleanup
-
----
-
-## 5. Known Limitations
-
-| Limitation | Impact | Mitigation |
-|-----------|--------|-----------|
-| Skill-embedded gates less reliable than hooks | Agent may ignore constraints | `<MANDATORY>` tags + Terminal State Checklist |
-| No physical file-system lock for freeze | Test files could be modified | Pre-Edit Gate + Terminal State verification |
-| Single model for all experts (degraded mode) | Loses cross-provider anonymity | Clearly label degraded reviews |
-| No `k6`/`locust` integration | Load testing limited | Future: MCP server for load testing |

package/skills/test-specification-alignment/evals/evals.json

@@ -1,75 +0,0 @@
-{
-  "skill_name": "test-specification-alignment",
-  "skill_path": "skills/test-specification-alignment/SKILL.md",
-  "evals": [
-    {
-      "id": 1,
-      "name": "aligned-tests-pass",
-      "category": "normal",
-      "prompt": "项目有specification.yaml定义了3个requirements和6个acceptance criteria。测试文件中有对应的@test REQ-001, @intent, @covers AC-001-01标注。请验证测试与specification的对齐情况。",
-      "expected_output": "执行完整两阶段流程：Phase 1验证对齐（检查@test/@intent/@covers标签、测试覆盖率、AC映射完整性）→对齐分数>=80%→Phase 2执行测试（冻结测试目录，禁止修改）→报告对齐结果。",
-      "files": [],
-      "assertions": [
-        {"name": "phase-1-executed", "type": "contains", "value": "Phase 1"},
-        {"name": "phase-2-executed", "type": "contains", "value": "Phase 2"},
-        {"name": "freeze-mentioned", "type": "contains", "value": "freeze"},
-        {"name": "alignment-score", "type": "regex", "value": "[0-9]+%"},
-        {"name": "test-annotations-checked", "type": "contains", "value": "@test"}
-      ]
-    },
-    {
-      "id": 2,
-      "name": "misaligned-tests-detected",
-      "category": "boundary",
-      "prompt": "项目有specification.yaml定义了5个requirements，但测试文件中只有2个@test标签，3个requirement没有对应测试。请验证对齐情况。",
-      "expected_output": "Phase 1应该检测到3个requirement缺少测试覆盖，对齐分数<80%。给出具体缺失项：哪些REQ没有@test标签，哪些AC没有@covers。可能需要Phase 1中添加缺失测试。",
-      "files": [],
-      "assertions": [
-        {"name": "missing-coverage-detected", "type": "contains", "value": "缺失"},
-        {"name": "low-alignment-score", "type": "contains", "value": "<80%"},
-        {"name": "specific-gaps-listed", "type": "contains", "value": "REQ"}
-      ]
-    },
-    {
-      "id": 3,
-      "name": "phase-2-freeze-enforcement",
-      "category": "boundary",
-      "prompt": "Phase 2执行测试时，有一个测试因为测试数据问题失败了。能不能修改一下测试数据让测试通过？",
-      "expected_output": "Phase 2期间绝对禁止修改测试文件（freeze约束）。失败应被分类（业务代码问题/测试数据问题/Specification问题/环境问题），但不能通过修改测试来解决。应告知这是零容忍原则。",
-      "files": [],
-      "assertions": [
-        {"name": "freeze-enforced", "type": "contains", "value": "禁止修改"},
-        {"name": "no-test-modification", "type": "not_contains", "value": "修改测试"},
-        {"name": "failure-classification", "type": "contains", "value": "分类"}
-      ]
-    },
-    {
-      "id": 4,
-      "name": "legacy-mode-no-specification",
-      "category": "boundary",
-      "prompt": "项目没有specification.yaml文件，需要验证测试覆盖率是否足够。请运行test-specification-alignment。",
-      "expected_output": "没有specification.yaml时进入legacy模式。应提示用户先通过delphi-review获得APPROVED后自动生成specification.yaml，而不是在没有spec的情况下进行对齐验证。",
-      "files": [],
-      "assertions": [
-        {"name": "specification-required", "type": "contains", "value": "specification.yaml"},
-        {"name": "legacy-mode-or-guidance", "type": "regex", "value": "(legacy|生成|delphi-review)"}
-      ]
-    }
-  ],
-  "trigger_evals": {
-    "should_trigger": [
-      "验证测试是否覆盖所有需求",
-      "测试和需求对齐了吗",
-      "run tests and check specification alignment",
-      "发布前验证测试覆盖率",
-      "verify tests before release"
-    ],
-    "should_not_trigger": [
-      "写一个新功能",
-      "帮我部署到生产环境",
-      "修复一个bug",
-      "代码review",
-      "设计数据库schema"
-    ]
-  }
-}