@boyingliu01/xp-gate 0.8.6 → 0.8.9

package/plugins/claude-code/skills/sprint-flow/AGENTS.md

@@ -1,68 +1,115 @@
 # SKILLS/SPRINT-FLOW KNOWLEDGE BASE
 
-**Generated:** 2026-05-30
-**Version:** v0.8.1
+**Generated:** 2026-06-11
+**Commit:** c18f82b
+**Branch:** main
+**Version:** 0.8.9.0
 
 ## OVERVIEW
-7-phase development pipeline: THINK→PLAN→BUILD→REVIEW→USER ACCEPT→FEEDBACK→SHIP, with ralph-loop default build mode.
+**11-phase** development pipeline: ISOLATE → AUTO-ESTIMATE → THINK → PLAN → BUILD → REVIEW → USER ACCEPTANCE → FEEDBACK → SHIP → LAND → CLEANUP. Phase 2 default build mode is **ralph-loop** (REQ-level iteration, 40-67% token savings vs parallel). HARD-GATE in Phase 1: design must pass Delphi review (≥91% consensus) before any coding.
+
+> **Doc drift**: README/CAPABILITIES still describe a "7-phase" pipeline. The canonical 11-phase model lives in `SKILL.md` and is what actually executes. See root `AGENTS.md` → "Known Drift" #4.
 
 ## STRUCTURE
 ```
 skills/sprint-flow/
-├── SKILL.md              # 7-phase pipeline definition
+├── SKILL.md              # 11-phase pipeline definition (canonical)
+├── AGENTS.md             # This file (mirrored to 7 other locations — DO NOT edit mirrors)
 ├── evals/                # Evaluation test cases
-├── evolution-history.json # Skill evolution tracking
-├── evolution-log.md      # Change history
-├── references/           # Phase reference docs
-│   ├── phase-0-think.md  # THINK phase guidelines
-│   └── ...               # Other phase docs
-└── templates/            # Sprint templates
+├── evolution-history.json
+├── evolution-log.md
+├── references/
+│   ├── phase-minus-0-5-auto-estimate.md  # Phase -0.5: AUTO-ESTIMATE
+│   ├── phase-0-think.md                   # Phase 0: brainstorming → CONTEXT.md + ADR
+│   ├── phase-1-plan.md                    # Phase 1: autoplan + delphi-review (HARD-GATE)
+│   ├── phase-2-build.md                   # Phase 2: ralph-loop default + TDD + test-align
+│   ├── phase-3-review.md                  # Phase 3: code-walkthrough + QA + benchmark
+│   ├── phase-4-uat.md                     # Phase 4: USER ACCEPTANCE
+│   ├── phase-5-feedback.md                # Phase 5: retro + debugging + learn
+│   ├── phase-6-ship.md                    # Phase 6: finishing-dev-branch + PR
+│   ├── phase-7-land.md                    # Phase 7: land + deploy
+│   ├── phase-8-cleanup.md                 # Phase 8: sprint branch cleanup
+│   ├── force-levels.md                    # Phase forcing rules
+│   └── components/                        # Reusable phase building blocks
+└── templates/
+    ├── auto-estimate-output-template.md
+    ├── auto-estimate-learning-log.md
+    ├── pain-document-template.md
+    ├── sprint-progress-template.md
+    ├── sprint-summary-template.md
+    └── emergent-issues-template.md
 ```
 
 ## WHERE TO LOOK
 | Task | Location | Notes |
 |------|----------|-------|
-| Pipeline def | SKILL.md | 7 phases with hard gates |
+| Pipeline definition | SKILL.md | 11 phases with HARD-GATE between Phase 1 and Phase 2 |
+| Auto-estimate phase | references/phase-minus-0-5-auto-estimate.md | Sizing pass before THINK |
 | THINK phase | references/phase-0-think.md | brainstorming → CONTEXT.md + ADR |
-| Build mode | SKILL.md | ralph-loop (default) vs parallel |
+| PLAN phase + HARD-GATE | references/phase-1-plan.md | autoplan → delphi-review → specification.yaml |
+| BUILD phase | references/phase-2-build.md | ralph-loop (default) vs parallel |
+| Force-level rules | references/force-levels.md | Defines when each phase becomes mandatory |
+| Templates | templates/ | Auto-estimate, sprint progress/summary, pain doc, emergent issues |
+
+## THE 11 PHASES
 
-## 7 PHASES
 | Phase | Name | Key Action | Hard Gate |
 |-------|------|-----------|-----------|
-| 0 | THINK | brainstorming, CONTEXT.md, ADR | — |
-| 1 | PLAN | autoplan → delphi-review → specification.yaml | HARD-GATE: design must pass |
-| 2 | BUILD | ralph-loop (REQ-level iteration) + TDD + test-align | — |
+| -1 | ISOLATE | Isolate working tree / worktree creation | — |
+| -0.5 | AUTO-ESTIMATE | Sizing pass; emits estimate template | — |
+| 0 | THINK | brainstorming → CONTEXT.md + ADR | — |
+| 1 | PLAN | autoplan → delphi-review → specification.yaml | **HARD-GATE**: design must reach ≥91% Delphi consensus |
+| 2 | BUILD | ralph-loop (REQ-level, default) + TDD + test-spec-alignment | — |
 | 3 | REVIEW | code-walkthrough + QA + benchmark | — |
-| 4 | USER ACCEPT | Manual verification | — |
-| 5 | FEEDBACK | Retro + debugging + learn | — |
-| 6 | SHIP | finishing-dev-branch + PR/merge | — |
+| 4 | USER ACCEPTANCE | Manual verification | — |
+| 5 | FEEDBACK | retro + debugging + `learn` (Sprint-level) | — |
+| 6 | SHIP | finishing-a-development-branch → PR | — |
+| 7 | LAND | land + deploy + canary | — |
+| 8 | CLEANUP | Sprint branch cleanup (per `docs/plans/2026-06-06-sprint-branch-cleanup-design.md`) | — |
 
 ## CONVENTIONS
-- ralph-loop is Phase 2 **default** mode (saves 40-67% tokens vs parallel)
-- delphi-review HARD-GATE in Phase 1: design unapproved → BLOCK coding
-- Each REQ in ralph-loop gets clean context (no linear accumulation)
-- `learn` called at Phase 5 + each REQ completion
+- **ralph-loop is Phase 2 default**. Each REQ runs in a clean context (no linear accumulation), saving 40-67% tokens vs parallel mode.
+- **delphi-review HARD-GATE in Phase 1**: design must reach ≥91% consensus across ≥2 model providers, domestic models only. Unapproved → BLOCK coding.
+- **`learn` is called twice**: once per REQ in Phase 2 (ralph-loop internal, `progress.log` permanent/contextual classification) and once in Phase 5 (Sprint-level retro).
+- **Phase isolation**: each phase has explicit entry/exit criteria documented in its `references/phase-*.md` file.
+- **Emergent Requirements** discovered in Phase 4 (USER ACCEPTANCE) are explicitly captured via `templates/emergent-issues-template.md` — never silently merged.
+- **Auto-detection**: Phase 0 uses `src/npm-package/lib/ui-detector.ts` to pick the right tech-stack templates.
 
 ## ANTI-PATTERNS (THIS PROJECT)
-- Do NOT skip delphi-review in Phase 1 — HARD-GATE blocks implementation
-- Do NOT use parallel build mode unless explicitly requested
-- Do NOT enter Phase 1 (PLAN) without completing THINK phase
-- DO NOT implement before design approval
+- Do NOT skip `delphi-review` in Phase 1 — HARD-GATE blocks implementation.
+- Do NOT use parallel build mode unless explicitly requested. Ralph-loop is the default for a reason.
+- Do NOT enter Phase 1 (PLAN) without completing Phase 0 (THINK).
+- Do NOT implement before design is APPROVED — Phase 1 must reach Delphi consensus first.
+- Do NOT merge an Emergent Requirement into the original Sprint silently — capture it via the template.
+- Do NOT terminate Delphi review before ≥91% consensus or 5 rounds, whichever first.
 
 ## UNIQUE STYLES
-- Auto-detects UI framework (ui-detector.ts in npm-package/lib/)
-- Supports --type and --lang flags for tech stack selection
-- Phase isolation: each phase has specific entry/exit criteria
-- Emergent Requirements acknowledged: user acceptance phase built in
+- **11 phases** including negative-numbered pre-phases (-1, -0.5) — intentional, captures the work that happens before "real" coding starts.
+- **HARD-GATE** between PLAN and BUILD is enforced both in the SKILL.md instructions and in the Claude Code plugin's PreToolUse hook (`plugins/claude-code/bin/delphi-review-guard.sh`).
+- **Per-REQ clean context in ralph-loop** = the core efficiency mechanism. Sprint-flow specifically chooses this over parallel mode.
+- **Tech-stack auto-detection** via `--type` and `--lang` flags or `ui-detector.ts`.
 
 ## COMMANDS
 ```bash
+/sprint-flow "开发用户登录"                                     # Full 11-phase pipeline
+/sprint-flow "开发用户登录" --type web-nextjs --lang typescript # Pin tech stack
+/sprint-flow "开发用户登录" --phase build-only                  # Skip planning (advanced)
+/sprint-flow "开发用户登录" --mode parallel                     # Legacy all-at-once (NOT default)
 /delphi-review "开发用户登录" --type web-nextjs --lang typescript
-/sprint-flow "开发用户登录" --phase build-only
-/sprint-flow "开发用户登录" --mode parallel  # Legacy all-at-once
 ```
 
 ## NOTES
-- Integrates brainstorming, autoplan, delphi-review, TDD, test-specification-alignment
-- ralph-loop internal learnings via progress.log (permanent/contextual classification)
-- Phase 5 calls gstack/learn for Sprint-level retrospective
+- Integrates: brainstorming, autoplan, delphi-review, TDD, test-specification-alignment, qa, design-review, benchmark, systematic-debugging, retro, learn, finishing-a-development-branch.
+- ralph-loop's internal learnings are persisted via `progress.log` (permanent vs contextual classification).
+- Phase 5 calls `gstack/learn` for Sprint-level retrospective.
+- Phase 8 cleanup behavior is governed by `docs/plans/2026-06-06-sprint-branch-cleanup-design.md`.
+- This `AGENTS.md` is the canonical version. **7 byte-identical mirrors** exist at:
+  - `plugins/claude-code/skills/sprint-flow/AGENTS.md`
+  - `plugins/opencode/skills/sprint-flow/AGENTS.md`
+  - `plugins/qoder/skills/sprint-flow/AGENTS.md`
+  - `src/npm-package/skills/sprint-flow/AGENTS.md`
+  - `src/npm-package/plugins/claude-code/skills/sprint-flow/AGENTS.md`
+  - `src/npm-package/plugins/opencode/skills/sprint-flow/AGENTS.md`
+  - `src/npm-package/plugins/qoder/skills/sprint-flow/AGENTS.md`
+  Mirrors are updated by `scripts/copy-skills.sh`. Do NOT edit them by hand.
+

package/plugins/claude-code/skills/test-driven-development/SKILL.md

@@ -1,71 +1,371 @@
 ---
 name: test-driven-development
-description: >
-  Test-Driven Development enforcement: RED → GREEN → REFACTOR cycle.
-  Write failing test first, then minimum code to pass, then refactor.
-  Includes Mock Usage Guidelines for integration-first testing.
-
-maturity: stable
+description: Use when implementing any feature or bugfix, before writing implementation code
 ---
 
-# Test-Driven Development
+# Test-Driven Development (TDD)
+
+## Overview
+
+Write the test first. Watch it fail. Write minimal code to pass.
+
+**Core principle:** If you didn't watch the test fail, you don't know if it tests the right thing.
+
+**Violating the letter of the rules is violating the spirit of the rules.**
+
+## When to Use
+
+**Always:**
+- New features
+- Bug fixes
+- Refactoring
+- Behavior changes
+
+**Exceptions (ask your human partner):**
+- Throwaway prototypes
+- Generated code
+- Configuration files
+
+Thinking "skip TDD just this once"? Stop. That's rationalization.
+
+## The Iron Law
+
+```
+NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST
+```
+
+Write code before the test? Delete it. Start over.
+
+**No exceptions:**
+- Don't keep it as "reference"
+- Don't "adapt" it while writing tests
+- Don't look at it
+- Delete means delete
+
+Implement fresh from tests. Period.
+
+## Red-Green-Refactor
+
+```dot
+digraph tdd_cycle {
+    rankdir=LR;
+    red [label="RED\nWrite failing test", shape=box, style=filled, fillcolor="#ffcccc"];
+    verify_red [label="Verify fails\ncorrectly", shape=diamond];
+    green [label="GREEN\nMinimal code", shape=box, style=filled, fillcolor="#ccffcc"];
+    verify_green [label="Verify passes\nAll green", shape=diamond];
+    refactor [label="REFACTOR\nClean up", shape=box, style=filled, fillcolor="#ccccff"];
+    next [label="Next", shape=ellipse];
 
-## Core Principles
+    red -> verify_red;
+    verify_red -> green [label="yes"];
+    verify_red -> red [label="wrong\nfailure"];
+    green -> verify_green;
+    verify_green -> refactor [label="yes"];
+    verify_green -> green [label="no"];
+    refactor -> verify_green [label="stay\ngreen"];
+    verify_green -> next;
+    next -> red;
+}
+```
+
+### RED - Write Failing Test
+
+Write one minimal test showing what should happen.
 
-| Principle | Description |
-|-----------|-------------|
-| **RED First** | Write a failing test before ANY implementation code |
-| **GREEN Minimum** | Write minimum code to pass the test — no extra features |
-| **REFACTOR** | Clean up code while keeping tests green |
-| **Delete & Restart** | If you write code before test — delete it and start over |
+<Good>
+```typescript
+test('retries failed operations 3 times', async () => {
+  let attempts = 0;
+  const operation = () => {
+    attempts++;
+    if (attempts < 3) throw new Error('fail');
+    return 'success';
+  };
 
-## Workflow
+  const result = await retryOperation(operation);
 
+  expect(result).toBe('success');
+  expect(attempts).toBe(3);
+});
 ```
-1. RED: Write failing test (describe/it + expect)
-2. GREEN: Write minimum implementation to pass
-3. REFACTOR: Clean up, extract, simplify — tests stay green
-4. Repeat for next behavior
+Clear name, tests real behavior, one thing
+</Good>
+
+<Bad>
+```typescript
+test('retry works', async () => {
+  const mock = jest.fn()
+    .mockRejectedValueOnce(new Error())
+    .mockRejectedValueOnce(new Error())
+    .mockResolvedValueOnce('success');
+  await retryOperation(mock);
+  expect(mock).toHaveBeenCalledTimes(3);
+});
 ```
+Vague name, tests mock not code
+</Bad>
+
+**Requirements:**
+- One behavior
+- Clear name
+- Real code (no mocks unless unavoidable)
+
+### Verify RED - Watch It Fail
+
+**MANDATORY. Never skip.**
+
+```bash
+npm test path/to/test.test.ts
+```
+
+Confirm:
+- Test fails (not errors)
+- Failure message is expected
+- Fails because feature missing (not typos)
+
+**Test passes?** You're testing existing behavior. Fix test.
+
+**Test errors?** Fix error, re-run until it fails correctly.
+
+### GREEN - Minimal Code
+
+Write simplest code to pass the test.
+
+<Good>
+```typescript
+async function retryOperation<T>(fn: () => Promise<T>): Promise<T> {
+  for (let i = 0; i < 3; i++) {
+    try {
+      return await fn();
+    } catch (e) {
+      if (i === 2) throw e;
+    }
+  }
+  throw new Error('unreachable');
+}
+```
+Just enough to pass
+</Good>
+
+<Bad>
+```typescript
+async function retryOperation<T>(
+  fn: () => Promise<T>,
+  options?: {
+    maxRetries?: number;
+    backoff?: 'linear' | 'exponential';
+    onRetry?: (attempt: number) => void;
+  }
+): Promise<T> {
+  // YAGNI
+}
+```
+Over-engineered
+</Bad>
+
+Don't add features, refactor other code, or "improve" beyond the test.
+
+### Verify GREEN - Watch It Pass
+
+**MANDATORY.**
+
+```bash
+npm test path/to/test.test.ts
+```
+
+Confirm:
+- Test passes
+- Other tests still pass
+- Output pristine (no errors, warnings)
+
+**Test fails?** Fix code, not test.
 
-## Mock Usage Guidelines (MANDATORY)
+**Other tests fail?** Fix now.
 
-### When to use mocks (ONLY these cases):
-1. External API/HTTP calls — use testcontainers or nock
-2. Database I/O — use in-memory DB (sqlite, testcontainers)
-3. File system I/O — use tmpdir / memfs
-4. Time-dependent code — inject clock dependency
-5. Non-deterministic behavior (random, UUID) — inject dependency
+### REFACTOR - Clean Up
 
-### When NOT to use mocks:
-- Pure business logic → test with real values
-- In-memory data transformations → test with real data
-- Validation logic → test with real input/output
-- State machines → test with real state transitions
+After green only:
+- Remove duplication
+- Improve names
+- Extract helpers
 
-### Mock Density Rule:
-If > 30% of test lines contain mock/spy/fn references,
-you are likely over-mocking. Add `// @mock-justified: <reason>` comment
-explaining why integration test is not feasible.
+Keep tests green. Don't add behavior.
 
-### Annotation Format:
+### Repeat
+
+Next failing test for next feature.
+
+## Good Tests
+
+| Quality | Good | Bad |
+|---------|------|-----|
+| **Minimal** | One thing. "and" in name? Split it. | `test('validates email and domain and whitespace')` |
+| **Clear** | Name describes behavior | `test('test1')` |
+| **Shows intent** | Demonstrates desired API | Obscures what code should do |
+
+## Why Order Matters
+
+**"I'll write tests after to verify it works"**
+
+Tests written after code pass immediately. Passing immediately proves nothing:
+- Might test wrong thing
+- Might test implementation, not behavior
+- Might miss edge cases you forgot
+- You never saw it catch the bug
+
+Test-first forces you to see the test fail, proving it actually tests something.
+
+**"I already manually tested all the edge cases"**
+
+Manual testing is ad-hoc. You think you tested everything but:
+- No record of what you tested
+- Can't re-run when code changes
+- Easy to forget cases under pressure
+- "It worked when I tried it" ≠ comprehensive
+
+Automated tests are systematic. They run the same way every time.
+
+**"Deleting X hours of work is wasteful"**
+
+Sunk cost fallacy. The time is already gone. Your choice now:
+- Delete and rewrite with TDD (X more hours, high confidence)
+- Keep it and add tests after (30 min, low confidence, likely bugs)
+
+The "waste" is keeping code you can't trust. Working code without real tests is technical debt.
+
+**"TDD is dogmatic, being pragmatic means adapting"**
+
+TDD IS pragmatic:
+- Finds bugs before commit (faster than debugging after)
+- Prevents regressions (tests catch breaks immediately)
+- Documents behavior (tests show how to use code)
+- Enables refactoring (change freely, tests catch breaks)
+
+"Pragmatic" shortcuts = debugging in production = slower.
+
+**"Tests after achieve the same goals - it's spirit not ritual"**
+
+No. Tests-after answer "What does this do?" Tests-first answer "What should this do?"
+
+Tests-after are biased by your implementation. You test what you built, not what's required. You verify remembered edge cases, not discovered ones.
+
+Tests-first force edge case discovery before implementing. Tests-after verify you remembered everything (you didn't).
+
+30 minutes of tests after ≠ TDD. You get coverage, lose proof tests work.
+
+## Common Rationalizations
+
+| Excuse | Reality |
+|--------|---------|
+| "Too simple to test" | Simple code breaks. Test takes 30 seconds. |
+| "I'll test after" | Tests passing immediately prove nothing. |
+| "Tests after achieve same goals" | Tests-after = "what does this do?" Tests-first = "what should this do?" |
+| "Already manually tested" | Ad-hoc ≠ systematic. No record, can't re-run. |
+| "Deleting X hours is wasteful" | Sunk cost fallacy. Keeping unverified code is technical debt. |
+| "Keep as reference, write tests first" | You'll adapt it. That's testing after. Delete means delete. |
+| "Need to explore first" | Fine. Throw away exploration, start with TDD. |
+| "Test hard = design unclear" | Listen to test. Hard to test = hard to use. |
+| "TDD will slow me down" | TDD faster than debugging. Pragmatic = test-first. |
+| "Manual test faster" | Manual doesn't prove edge cases. You'll re-test every change. |
+| "Existing code has no tests" | You're improving it. Add tests for existing code. |
+
+## Red Flags - STOP and Start Over
+
+- Code before test
+- Test after implementation
+- Test passes immediately
+- Can't explain why test failed
+- Tests added "later"
+- Rationalizing "just this once"
+- "I already manually tested it"
+- "Tests after achieve the same purpose"
+- "It's about spirit not ritual"
+- "Keep as reference" or "adapt existing code"
+- "Already spent X hours, deleting is wasteful"
+- "TDD is dogmatic, I'm being pragmatic"
+- "This is different because..."
+
+**All of these mean: Delete code. Start over with TDD.**
+
+## Example: Bug Fix
+
+**Bug:** Empty email accepted
+
+**RED**
 ```typescript
-// @mock-justified: external API wrapper, no sandbox environment available
+test('rejects empty email', async () => {
+  const result = await submitForm({ email: '' });
+  expect(result.error).toBe('Email required');
+});
 ```
-Reason text must be at least 10 characters. Bare `@mock-justified` without colon+reason is invalid.
 
-## Test Annotations
+**Verify RED**
+```bash
+$ npm test
+FAIL: expected 'Email required', got undefined
+```
 
+**GREEN**
 ```typescript
-/**
- * @test REQ-XXX Feature name
- * @intent Verify specific behavior
- * @covers AC-XXX-01, AC-XXX-02
- */
+function submitForm(data: FormData) {
+  if (!data.email?.trim()) {
+    return { error: 'Email required' };
+  }
+  // ...
+}
 ```
 
-## Coverage Requirements
+**Verify GREEN**
+```bash
+$ npm test
+PASS
+```
+
+**REFACTOR**
+Extract validation for multiple fields if needed.
+
+## Verification Checklist
+
+Before marking work complete:
+
+- [ ] Every new function/method has a test
+- [ ] Watched each test fail before implementing
+- [ ] Each test failed for expected reason (feature missing, not typo)
+- [ ] Wrote minimal code to pass each test
+- [ ] All tests pass
+- [ ] Output pristine (no errors, warnings)
+- [ ] Tests use real code (mocks only if unavoidable)
+- [ ] Edge cases and errors covered
+
+Can't check all boxes? You skipped TDD. Start over.
+
+## When Stuck
+
+| Problem | Solution |
+|---------|----------|
+| Don't know how to test | Write wished-for API. Write assertion first. Ask your human partner. |
+| Test too complicated | Design too complicated. Simplify interface. |
+| Must mock everything | Code too coupled. Use dependency injection. |
+| Test setup huge | Extract helpers. Still complex? Simplify design. |
+
+## Debugging Integration
+
+Bug found? Write failing test reproducing it. Follow TDD cycle. Test proves fix and prevents regression.
+
+Never fix bugs without a test.
+
+## Testing Anti-Patterns
+
+When adding mocks or test utilities, read @testing-anti-patterns.md to avoid common pitfalls:
+- Testing mock behavior instead of real behavior
+- Adding test-only methods to production classes
+- Mocking without understanding dependencies
+
+## Final Rule
+
+```
+Production code → test exists and failed first
+Otherwise → not TDD
+```
 
-- Minimum 80% line coverage
-- All acceptance criteria must have corresponding tests
-- Tests must survive mutation testing (Gate M pre-push)
+No exceptions without your human partner's permission.