@guanlin4924/devflow-pi 0.1.21 → 0.1.23

package/plugins/devflow-quality/skills/workflow-complete-milestone/references/milestone-archive.md

@@ -1,123 +0,0 @@
-# Milestone Archive Template
-
-This template is used by the complete-milestone workflow to create archive files in `.planning/milestones/`.
-
----
-
-## File Template
-
-# Milestone v{{VERSION}}: {{MILESTONE_NAME}}
-
-**Status:** ✅ SHIPPED {{DATE}}
-**Phases:** {{PHASE_START}}-{{PHASE_END}}
-**Total Plans:** {{TOTAL_PLANS}}
-
-## Overview
-
-{{MILESTONE_DESCRIPTION}}
-
-## Phases
-
-{{PHASES_SECTION}}
-
-[For each phase in this milestone, include:]
-
-### Phase {{PHASE_NUM}}: {{PHASE_NAME}}
-
-**Goal**: {{PHASE_GOAL}}
-**Depends on**: {{DEPENDS_ON}}
-**Plans**: {{PLAN_COUNT}} plans
-
-Plans:
-
-- [x] {{PHASE}}-01: {{PLAN_DESCRIPTION}}
-- [x] {{PHASE}}-02: {{PLAN_DESCRIPTION}}
-      [... all plans ...]
-
-**Details:**
-{{PHASE_DETAILS_FROM_ROADMAP}}
-
-**For decimal phases, include (INSERTED) marker:**
-
-### Phase 2.1: Critical Security Patch (INSERTED)
-
-**Goal**: Fix authentication bypass vulnerability
-**Depends on**: Phase 2
-**Plans**: 1 plan
-
-Plans:
-
-- [x] 02.1-01: Patch auth vulnerability
-
-**Details:**
-{{PHASE_DETAILS_FROM_ROADMAP}}
-
----
-
-## Milestone Summary
-
-**Decimal Phases:**
-
-- Phase 2.1: Critical Security Patch (inserted after Phase 2 for urgent fix)
-- Phase 5.1: Performance Hotfix (inserted after Phase 5 for production issue)
-
-**Key Decisions:**
-{{DECISIONS_FROM_PROJECT_STATE}}
-[Example:]
-
-- Decision: Use ROADMAP.md split (Rationale: Constant context cost)
-- Decision: Decimal phase numbering (Rationale: Clear insertion semantics)
-
-**Issues Resolved:**
-{{ISSUES_RESOLVED_DURING_MILESTONE}}
-[Example:]
-
-- Fixed context overflow at 100+ phases
-- Resolved phase insertion confusion
-
-**Issues Deferred:**
-{{ISSUES_DEFERRED_TO_LATER}}
-[Example:]
-
-- PROJECT-STATE.md tiering (deferred until decisions > 300)
-
-**Technical Debt Incurred:**
-{{SHORTCUTS_NEEDING_FUTURE_WORK}}
-[Example:]
-
-- Some workflows still have hardcoded paths (fix in Phase 5)
-
----
-
-_For current project status, see .planning/ROADMAP.md_
-
----
-
-## Usage Guidelines
-
-<guidelines>
-**When to create milestone archives:**
-- After completing all phases in a milestone (v1.0, v1.1, v2.0, etc.)
-- Triggered by complete-milestone workflow
-- Before planning next milestone work
-
-**How to fill template:**
-
-- Replace {{PLACEHOLDERS}} with actual values
-- Extract phase details from ROADMAP.md
-- Document decimal phases with (INSERTED) marker
-- Include key decisions from PROJECT-STATE.md or SUMMARY files
-- List issues resolved vs deferred
-- Capture technical debt for future reference
-
-**Archive location:**
-
-- Save to `.planning/milestones/v{VERSION}-{NAME}.md`
-- Example: `.planning/milestones/v1.0-mvp.md`
-
-**After archiving:**
-
-- Update ROADMAP.md to collapse completed milestone in `<details>` tag
-- Update PROJECT.md to brownfield format with Current State section
-- Continue phase numbering in next milestone (never restart at 01)
-  </guidelines>

package/plugins/devflow-quality/skills/workflow-verify-work/SKILL.md

@@ -1,112 +0,0 @@
----
-name: workflow-verify-work
-description: "Use when implemented features need UAT, verification evidence, user-facing behavior checks, or failure routing before milestone audit."
----
-
-<objective>
-Validate built features through conversational testing with persistent state.
-
-Purpose: Confirm what the agent built actually works from the user's perspective. One test at a time, plain text responses, no interrogation. When issues are found, automatically diagnose, plan fixes, and prepare for execution.
-
-Output:
-- `{phase_num}-UAT.md` — raw test log (items, results, user responses)
-- `{phase_num}-VERIFICATION.md` — formal verification report mapping REQ-IDs / FP-IDs to passed UAT items, with evidence summary and closure statement. Must be generated when all UAT items pass (no failures, no skips that block closure). If VERIFICATION.md already exists from execute-phase, merge UAT results into it rather than creating a duplicate.
-- `.planning/phases/{phase}/01-VERIFICATION.meta.json` — structured metadata (`uat_passed`, `uat_failed`, `uat_skipped`, `gate_passed`, `gate_total`, `known_issues`). Schema in `feature-development.yaml` under `steps[verify].meta_output.fields`.
-</objective>
-
-<execution_context>
-references/verify-work.md
-assets/UAT.md
-</execution_context>
-
-<context>
-Phase: $ARGUMENTS (optional)
-- If provided: Test specific phase (e.g., "4")
-- If not provided: Check for active sessions or prompt for phase
-
-**Project rule package:**
-During verification, discover and read applicable rule sources:
-- `.planning/rules/INDEX.md`
-- `.planning/execution-contract.md`
-- `.planning/toolchain.md`
-- `.planning/lessons/README.md`
-- `.planning/milestones/`
-- `.planning/requirements/`
-- `.planning/code-index/`
-- `.context/spec/`
-- `.context/workflow/verification.md`
-- `.context/workflow/checklist.md`
-- `.context/lessons/README.md`（如存在）
-- root `AGENTS.md`, `CLAUDE.md`, or equivalent project instruction files
-
-Context files are resolved inside the workflow (`init verify-work`) and delegated via `<files_to_read>` blocks.
-Use `.planning/milestones/`, `.planning/requirements/`, `.planning/lessons/`, and phase `CONTEXT.md` as primary history when verification needs prior decisions. Treat `features/` or `.context/lessons/` as optional legacy/project-rule sources only when present.
-</context>
-
-<verification_gates>
-Verification must include these gates when project artifacts exist:
-
-1. **Change-list consistency gate**
-   - Locate the relevant `.planning/features/**/*变更清单.md` or phase plan. If missing, check legacy `features/**/*变更清单.md`.
-   - Check expected changes against implementation.
-   - If `.planning/code-index/` exists, use it to verify changed files, symbols, callers/callees, imports, and resource reads/writes before source readback.
-   - Report missing implementation, extra implementation, and deviations before functional UAT conclusions.
-
-2. **Project rule review gate**
-   - Review changed files against applicable project rules, task-level rules, and lessons.
-   - Existing code style may inform local patterns but must not override explicit project rules.
-   - Review the whole changed file or component boundary, not only the diff, when the project rules apply at file or layer level.
-   - Check both omissions and extras: missing required pieces, extra unplanned code, unused imports/fields/methods, stale generated artifacts, and duplicated implementations.
-   - If issues exist, produce a fix list and route back to execution.
-
-3. **Mainflow automation gate**
-   - Read `.planning/phases/{phase}/MAINFLOW-CASES.md`, `.planning/generated-cases/{feature}/validation-report.md`, and `.planning/generated-cases/{feature}/case-import-payloads.json` when they exist.
-   - If generated DSL validation failed, UAT does not pass.
-   - If mainflow case execution failed after import or direct execution, UAT does not pass.
-   - If environment or platform dependencies are missing and execution cannot run, mark verification `blocked`, not passed.
-   - If cases were not imported into the platform, complete at least static validation and record that import/execution remains pending.
-   - If cases were imported into the platform, record `execution_id` and execution result for each imported mainflow case.
-   - Mainflow cases must be limited to `api-mainflow` and `ui-mainflow`; any non-mainflow tag is a gate failure.
-
-4. **Toolchain and test gate**
-   - Run or require the commands declared by `.planning/toolchain.md`, `.planning/execution-contract.md`, `.context/workflow/verification.md`, or the change list.
-   - Include target tests, full tests, build, codegen/mock/DI checks, migration checks, and integration tests when applicable.
-
-5. **冻结验收测试门禁**
-   - 读取 `.planning/requirements/{feature}/tests.json`、`.planning/features/{feature}/acceptance-test-bindings.json` 和 `.planning/test-runs/{feature}/acceptance-results.json`。
-   - 调用 `devflow_run_acceptance_tests(action="validate_results", feature=...)`；它验证结果仍引用当前冻结 suite，且每个 `TC-*` 都已通过。
-   - 任一 TC 未执行、失败、人工待执行或因环境阻塞时，验证状态只能是 `blocked` 或 `failed`，CP-4 不得宣称验收通过。
-   - Markdown、UAT 口述或 agent 自述不能替代该 Core-owned 结果。
-
-6. **Compatibility gate**
-   - Check interface, database, config, data migration, permission, and consumer compatibility risks.
-   - For frontend-visible API/VO/schema changes, record backward compatibility or migration handling.
-   - For database/model/config changes, record migration, rollback, and deployment ordering risk.
-   - Record accepted residual risks explicitly.
-
-7. **Baseline decision gate**
-   - Compare implementation against `.planning/requirements/baseline.md`, especially `反向审视与用户拍板`, `待确认事项`, and `下游输入契约`.
-   - Confirm implemented behavior maps to `FP-*`, `BR-*`, `BC-*`, and confirmed `CR-*` decisions.
-   - Any implemented scope based on a pending decision is a verification failure unless the user explicitly approved it.
-
-8. **Lessons extraction gate**
-   - After verification is complete, review the findings for lessons worth preserving.
-   - Candidate triggers for a lesson:
-     - A regression was caught early — what pattern prevented it?
-     - A non-obvious interaction between modules was discovered
-     - A test gap was identified that exists beyond this feature
-     - A design decision was made that future tasks must reference
-   - If a lesson candidate exists, write to `.context/lessons/YYYY-MM-DD-{slug}.md`.
-   - If no candidate, skip.
-   - This gate covers both positive patterns (successful approach worth repeating) and negative patterns (regression prevention).
-
-The feature is complete only when UAT, mainflow automation, baseline decision, consistency, project rule review, compatibility, and required toolchain/test gates pass or have explicit user-approved exceptions.
-
-When all gates pass: write `VERIFICATION.md` before exiting. This is non-negotiable — downstream `workflow-audit-milestone` requires it.
-</verification_gates>
-
-<process>
-Execute the verify-work workflow from references/verify-work.md end-to-end.
-Preserve all workflow gates (session management, test presentation, diagnosis, fix planning, routing).
-Additionally preserve the verification gates above before declaring the work complete.
-</process>

package/plugins/devflow-quality/skills/workflow-verify-work/assets/UAT.md

@@ -1,265 +0,0 @@
-# UAT Template
-
-Template for `.planning/phases/XX-name/{phase_num}-UAT.md` — persistent UAT session tracking.
-
----
-
-## File Template
-
-```markdown
----
-status: testing | partial | complete | diagnosed
-phase: XX-name
-source: [list of SUMMARY.md files tested]
-started: [ISO timestamp]
-updated: [ISO timestamp]
----
-
-## Current Test
-<!-- OVERWRITE each test - shows where we are -->
-
-number: [N]
-name: [test name]
-expected: |
-  [what user should observe]
-awaiting: user response
-
-## Tests
-
-### 1. [Test Name]
-expected: [observable behavior - what user should see]
-result: [pending]
-
-### 2. [Test Name]
-expected: [observable behavior]
-result: pass
-
-### 3. [Test Name]
-expected: [observable behavior]
-result: issue
-reported: "[verbatim user response]"
-severity: major
-
-### 4. [Test Name]
-expected: [observable behavior]
-result: skipped
-reason: [why skipped]
-
-### 5. [Test Name]
-expected: [observable behavior]
-result: blocked
-blocked_by: server | physical-device | release-build | third-party | prior-phase
-reason: [why blocked]
-
-...
-
-## Summary
-
-total: [N]
-passed: [N]
-issues: [N]
-pending: [N]
-skipped: [N]
-blocked: [N]
-
-## Gaps
-
-<!-- YAML format for plan-phase --gaps consumption -->
-- truth: "[expected behavior from test]"
-  status: failed
-  reason: "User reported: [verbatim response]"
-  severity: blocker | major | minor | cosmetic
-  test: [N]
-  root_cause: ""     # Filled by diagnosis
-  artifacts: []      # Filled by diagnosis
-  missing: []        # Filled by diagnosis
-  debug_session: ""  # Filled by diagnosis
-```
-
----
-
-<section_rules>
-
-**Frontmatter:**
-- `status`: OVERWRITE - "testing", "partial", or "complete"
-- `phase`: IMMUTABLE - set on creation
-- `source`: IMMUTABLE - SUMMARY files being tested
-- `started`: IMMUTABLE - set on creation
-- `updated`: OVERWRITE - update on every change
-
-**Current Test:**
-- OVERWRITE entirely on each test transition
-- Shows which test is active and what's awaited
-- On completion: "[testing complete]"
-
-**Tests:**
-- Each test: OVERWRITE result field when user responds
-- `result` values: [pending], pass, issue, skipped, blocked
-- If issue: add `reported` (verbatim) and `severity` (inferred)
-- If skipped: add `reason` if provided
-- If blocked: add `blocked_by` (tag) and `reason` (if provided)
-
-**Summary:**
-- OVERWRITE counts after each response
-- Tracks: total, passed, issues, pending, skipped
-
-**Gaps:**
-- APPEND only when issue found (YAML format)
-- After diagnosis: fill `root_cause`, `artifacts`, `missing`, `debug_session`
-- This section feeds directly into /workflow-pipeline --gaps
-
-</section_rules>
-
-<diagnosis_lifecycle>
-
-**After testing complete (status: complete), if gaps exist:**
-
-1. User runs diagnosis (from verify-work offer or manually)
-2. diagnose-issues workflow spawns parallel debug agents
-3. Each agent investigates one gap, returns root cause
-4. UAT.md Gaps section updated with diagnosis:
-   - Each gap gets `root_cause`, `artifacts`, `missing`, `debug_session` filled
-5. status → "diagnosed"
-6. Ready for /workflow-pipeline --gaps with root causes
-
-**After diagnosis:**
-```yaml
-## Gaps
-
-- truth: "Comment appears immediately after submission"
-  status: failed
-  reason: "User reported: works but doesn't show until I refresh the page"
-  severity: major
-  test: 2
-  root_cause: "useEffect in CommentList.tsx missing commentCount dependency"
-  artifacts:
-    - path: "src/components/CommentList.tsx"
-      issue: "useEffect missing dependency"
-  missing:
-    - "Add commentCount to useEffect dependency array"
-  debug_session: ".planning/debug/comment-not-refreshing.md"
-```
-
-</diagnosis_lifecycle>
-
-<lifecycle>
-
-**Creation:** When /workflow-verify-work starts new session
-- Extract tests from SUMMARY.md files
-- Set status to "testing"
-- Current Test points to test 1
-- All tests have result: [pending]
-
-**During testing:**
-- Present test from Current Test section
-- User responds with pass confirmation or issue description
-- Update test result (pass/issue/skipped)
-- Update Summary counts
-- If issue: append to Gaps section (YAML format), infer severity
-- Move Current Test to next pending test
-
-**On completion:**
-- status → "complete"
-- Current Test → "[testing complete]"
-- Commit file
-- Present summary with next steps
-
-**Partial completion:**
-- status → "partial" (if pending, blocked, or unresolved skipped tests remain)
-- Current Test → "[testing paused — {N} items outstanding]"
-- Commit file
-- Present summary with outstanding items highlighted
-
-**Resuming partial session:**
-- `/workflow-verify-work {phase}` picks up from first pending/blocked test
-- When all items resolved, status advances to "complete"
-
-**Resume after /clear:**
-1. Read frontmatter → know phase and status
-2. Read Current Test → know where we are
-3. Find first [pending] result → continue from there
-4. Summary shows progress so far
-
-</lifecycle>
-
-<severity_guide>
-
-Severity is INFERRED from user's natural language, never asked.
-
-| User describes | Infer |
-|----------------|-------|
-| Crash, error, exception, fails completely, unusable | blocker |
-| Doesn't work, nothing happens, wrong behavior, missing | major |
-| Works but..., slow, weird, minor, small issue | minor |
-| Color, font, spacing, alignment, visual, looks off | cosmetic |
-
-Default: **major** (safe default, user can clarify if wrong)
-
-</severity_guide>
-
-<good_example>
-```markdown
----
-status: diagnosed
-phase: 04-comments
-source: 04-01-SUMMARY.md, 04-02-SUMMARY.md
-started: 2025-01-15T10:30:00Z
-updated: 2025-01-15T10:45:00Z
----
-
-## Current Test
-
-[testing complete]
-
-## Tests
-
-### 1. View Comments on Post
-expected: Comments section expands, shows count and comment list
-result: pass
-
-### 2. Create Top-Level Comment
-expected: Submit comment via rich text editor, appears in list with author info
-result: issue
-reported: "works but doesn't show until I refresh the page"
-severity: major
-
-### 3. Reply to a Comment
-expected: Click Reply, inline composer appears, submit shows nested reply
-result: pass
-
-### 4. Visual Nesting
-expected: 3+ level thread shows indentation, left borders, caps at reasonable depth
-result: pass
-
-### 5. Delete Own Comment
-expected: Click delete on own comment, removed or shows [deleted] if has replies
-result: pass
-
-### 6. Comment Count
-expected: Post shows accurate count, increments when adding comment
-result: pass
-
-## Summary
-
-total: 6
-passed: 5
-issues: 1
-pending: 0
-skipped: 0
-
-## Gaps
-
-- truth: "Comment appears immediately after submission in list"
-  status: failed
-  reason: "User reported: works but doesn't show until I refresh the page"
-  severity: major
-  test: 2
-  root_cause: "useEffect in CommentList.tsx missing commentCount dependency"
-  artifacts:
-    - path: "src/components/CommentList.tsx"
-      issue: "useEffect missing dependency"
-  missing:
-    - "Add commentCount to useEffect dependency array"
-  debug_session: ".planning/debug/comment-not-refreshing.md"
-```
-</good_example>