[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EGENJJFC46DX27QJNDJKYP":3,"skill-same:01M6EGENJJFC46DX27QJNDJKYP":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":27,"linkOnly":28,"markdownContent":29,"markdownBody":30,"frontMatter":31,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":35,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":38,"ownerDescription":39,"updatedAt":40,"install":41,"resources":54},"01M6EGENJJFC46DX27QJNDJKYP","ln-500-story-quality-gate",null,"Story-level quality orchestrator with 4-level Gate (PASS\u002FCONCERNS\u002FFAIL\u002FWAIVED) and Quality Score. Delegates to ln-510 (quality) and ln-520 (tests), calculates final verdict.","levalencia\u002Fagent-god-mode","levalencia","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6962857?v=4","01M6EB0FZZ4BPQPC4HET4QY6NM","Luis Valencia ","01M6EB0G4HWHPWW0H9X7QKSAHP",3,"MIT","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-500-story-quality-gate\u002FSKILL.md",[],[19,20,21,22,23,24,25,26],"quality gate","quality","Story","gate","ln 500 story quality gate","orchestrator","tests","verdict","2026-11-10 10:12:30",false,"---\nname: ln-500-story-quality-gate\ndescription: \"Story-level quality orchestrator with 4-level Gate (PASS\u002FCONCERNS\u002FFAIL\u002FWAIVED) and Quality Score. Delegates to ln-510 (quality) and ln-520 (tests), calculates final verdict.\"\nlicense: MIT\n---\n\n> **Paths:** File paths (`shared\u002F`, `references\u002F`, `..\u002Fln-*`) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.\n\n# Story Quality Gate\n\nThin orchestrator that coordinates quality checks and test planning, then determines final Story verdict.\n\n## Inputs\n\n| Input | Required | Source | Description |\n|-------|----------|--------|-------------|\n| `storyId` | Yes | args, git branch, kanban, user | Story to process |\n\n**Resolution:** Story Resolution Chain.\n**Status filter:** To Review\n\n## Purpose & Scope\n- Invoke ln-510-quality-coordinator for code quality checks\n- Invoke ln-520-test-planner for test planning (if needed)\n- Calculate Quality Score and NFR validation\n- Determine 4-level Gate verdict (PASS\u002FCONCERNS\u002FFAIL\u002FWAIVED)\n- Mark Story as Done or create fix tasks\n- Delegates ALL work — never runs checks directly\n\n## 4-Level Gate Model\n\n| Level | Meaning | Action |\n|-------|---------|--------|\n| **PASS** | All checks pass, no issues | Story -> Done |\n| **CONCERNS** | Minor issues, acceptable risk | Story -> Done with comment noting concerns |\n| **FAIL** | Blocking issues found | Create fix tasks, return to ln-400 |\n| **WAIVED** | Issues acknowledged by user | Story -> Done with waiver reason documented |\n\n**Verdict calculation:** `FAIL` if any check fails. `CONCERNS` if minor issues exist. `PASS` if all clean.\n\n## Quality Score\n\nFormula: `Quality Score = 100 - (20 x FAIL_count) - (10 x CONCERN_count)`\n\n| Score Range | Status | Action |\n|-------------|--------|--------|\n| 90-100 | Excellent | PASS |\n| 70-89 | Acceptable | CONCERNS (proceed with notes) |\n| 50-69 | Below threshold | FAIL (create fix tasks) |\n| \u003C50 | Critical | FAIL (urgent priority) |\n\n## NFR Validation\n\n| NFR | Checks | Issue Prefix |\n|-----|--------|--------------|\n| **Security** | Auth, input validation, secrets exposure | SEC- |\n| **Performance** | N+1 queries, caching, response times | PERF- |\n| **Maintainability** | DRY, SOLID, cyclomatic complexity, error handling | MNT- |\n\nAdditional prefixes: `TEST-` (coverage gaps), `ARCH-` (architecture), `DOC-` (documentation), `DEP-` (dependencies), `COV-` (AC coverage), `DB-` (database schema), `AC-` (AC validation)\n\n## When to Use\n- All implementation tasks in Story are Done\n- User requests quality gate for Story\n- ln-400-story-executor delegates quality check\n\n## Workflow\n\n### Phase 0: Tools Config\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Ftools_config_guide.md`, `shared\u002Freferences\u002Fstorage_mode_detection.md`, and `shared\u002Freferences\u002Finput_resolution_pattern.md`\n\nExtract: `task_provider` = Task Management → Provider (`linear` | `file`).\n\n### Phase 1: Discovery\n\n1) **Resolve storyId:** Run Story Resolution Chain per guide (status filter: [To Review]).\n2) Auto-discover team\u002Fconfig from `docs\u002Ftasks\u002Fkanban_board.md`\n3) Load Story + task metadata:\n   - IF `task_provider` = `linear`: `get_issue(storyId)` + `list_issues(parentId=storyId)`\n   - IF `task_provider` = `file`: `Read story.md` + `Glob(\"docs\u002Ftasks\u002Fepics\u002F*\u002Fstories\u002F*\u002Ftasks\u002F*.md\")`\n4) Detect test task status (exists? Done?)\n\n### Phase 2: Fast-Track Decision\n\nStories with high readiness (validated pre-execution) can skip expensive checks.\n\n```\nIF readiness_score available in CONTEXT:\n  IF readiness_score == 10:\n    fast_track = true\n  ELSE:\n    fast_track = false\nELSE:\n  fast_track = false    # No readiness data — full gate\n```\n\n**Fast-track matrix (readiness == 10):**\n\n| Component | Full Gate | Fast-Track | Why |\n|-----------|-----------|------------|-----|\n| ln-513 regression tests | RUN | RUN | Always critical, cheap |\n| Linters | RUN | RUN | Cheap, catches formatting |\n| Criteria Validation (3 checks) | RUN | RUN | Cheap, validates AC coverage |\n| ln-511 metrics + static analysis | RUN | **RUN** | **Catches complexity\u002FDRY\u002Fdead code that per-task review misses** |\n| ln-511 MCP Ref (OPT-, BP-, PERF-) | RUN | **SKIP** | Expensive external calls |\n| Inline agent review | RUN | **RUN (1 agent minimum)** | Catches logic\u002Falgorithm bugs that static analysis misses |\n| ln-520 test planning | RUN | **SKIP** | Redundant for pre-validated |\n| NFR validation | All dims | **Security only** | Perf\u002FMaintainability less critical |\n\n### Phase 3: Quality Checks (delegate to ln-510)\n\n1) **Invoke ln-510-quality-coordinator** via Skill tool\n   - Pass: Story ID (+ `--fast-track` flag if fast_track == true)\n   - Full: ln-510 runs: code quality (ln-511) -> criteria validation -> linters -> regression (ln-513)\n   - Fast-track: ln-510 runs: code metrics + static (ln-511 `--skip-mcp-ref`) -> criteria -> linters -> regression (ln-513) — skips MCP Ref\u002Fagent review\n2) **If ln-510 returns FAIL:**\n   - Create fix\u002Frefactor tasks via ln-301\n   - Stop — return to ln-400\n\n### Phase 4: Test Planning (delegate to ln-520)\n\n1) **IF fast_track: SKIP Phase 4 entirely** (proceed to Phase 5)\n2) Check test task status:\n   - **No test task** -> invoke ln-520-test-planner to create\n   - **Test task exists, not Done** -> report status, stop\n   - **Test task Done** -> proceed to Phase 5\n\n3) **Invoke ln-520-test-planner** via Skill tool (if needed)\n   - Pass: Story ID\n   - ln-520 runs: research (ln-521) -> manual testing (ln-522) -> auto test planning (ln-523)\n\n### Phase 5: Test Verification (after test task Done)\n\n1) Load test task:\n   - IF `task_provider` = `linear`: `get_issue(testTaskId)`\n   - IF `task_provider` = `file`: `Read` test task file from `docs\u002Ftasks\u002Fepics\u002F...\u002Ftasks\u002FT{NNN}-*.md`\n2) Verify limits and priority:\n   - Priority ≥15 scenarios covered\n   - Each test passes Usefulness Criteria (no numerical targets)\n   - Tests focus on business logic (no framework\u002FDB\u002Flibrary tests)\n3) Verify Story AC coverage by tests\n4) Check infra\u002Fdocs updates present\n\n### Phase 6: Final Verdict\n\n1) **Calculate Quality Score** (see formula above)\n2) **Run NFR checks** per dimensions table (fast_track: Security only; full: all dimensions)\n3) **Assign issue prefixes:** SEC-, PERF-, MNT-, TEST-, ARCH-, DOC-\n4) **Determine Gate verdict** per 4-Level Gate Model\n5) Post gate verdict comment:\n   - IF `task_provider` = `linear`: `create_comment({issueId: storyId, body: verdict_summary})`\n   - IF `task_provider` = `file`: `Write` comment to `docs\u002Ftasks\u002Fepics\u002F...\u002Fcomments\u002F{ISO-timestamp}.md`\n6) **If FAIL:** Record root cause analysis — classify each failure (missing_context | wrong_pattern | unclear_ac | doc_gap | test_gap). Append to `docs\u002Fproject\u002Farchitecture_health.md` under `## Root Cause Log` (create section if missing). Format: `| {date} | {story_id} | {issue_id} | {classification} | {action_taken} |`\n7) **Escaped defects (post-gate):** When bugs are discovered AFTER gate verdict (manual review, production, ln-310 mode=code_review), run Detection Efficacy Audit per `shared\u002Freferences\u002Fdetection_efficacy_audit.md`. Log results to `docs\u002Fproject\u002Farchitecture_health.md` under `## Escaped Defect Log`. Classifications: `algorithm_logic | performance_pattern | domain_specific | resource_bounds | encapsulation | data_structure | concurrency`.\n8) Update Story status:\n   - IF `task_provider` = `linear`: `save_issue({id: storyId, state: \"Done\"})` for PASS\u002FCONCERNS\u002FWAIVED; create fix tasks for FAIL\n   - IF `task_provider` = `file`: `Edit` `**Status:**` line to `Done` in story.md for PASS\u002FCONCERNS\u002FWAIVED; create fix task files for FAIL\n\n### Phase 7: Branch Finalization\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Fgit_worktree_fallback.md`\n\nRuns only when verdict is PASS, CONCERNS, or WAIVED. Consumes verified results from ln-510\u002Fln-513 — does NOT rerun checks.\n\n1. IF uncommitted changes exist → `git add -A && git commit -m \"{storyId}: {Story Title}\"`\n2. Push branch: `git push -u origin {branch}`\n3. Move Story + Tasks → Done (Linear or kanban)\n4. Report to chat + file: branch name, git stats (files changed, insertions, deletions), quality verdict\n5. Cleanup: `git worktree remove {worktree_dir}` (branch preserved on remote)\n\n**On FAIL verdict:** Skip Phase 7. Create fix tasks, return to ln-400.\n\n**TodoWrite format (mandatory):**\n```\n- Invoke ln-510-quality-coordinator (in_progress)\n- Check test task status (pending)\n- Invoke ln-520-test-planner (pending, if needed)\n- Verify test coverage (pending)\n- Calculate Quality Score + NFR (pending)\n- Determine verdict + update Story (pending)\n- Branch finalization (pending)\n```\n\n## Worker Invocation (MANDATORY)\n\n| Phase | Worker | Purpose |\n|-------|--------|---------|\n| 3 | ln-510-quality-coordinator | Code quality + criteria + linters + regression |\n| 4 | ln-520-test-planner | Research + manual testing + auto test planning |\n\n**Invocation:**\n```\nSkill(skill: \"ln-510-quality-coordinator\", args: \"{storyId}\")\nSkill(skill: \"ln-520-test-planner\", args: \"{storyId}\")\n```\n\n**Anti-Patterns:**\n- Running mypy, ruff, pytest directly instead of invoking ln-510\n- Running web searches or creating bash scripts instead of invoking ln-520\n- Marking steps as completed without invoking the actual skill\n- Any direct command execution that should be delegated\n\n## Critical Rules\n- Early-exit: any failure creates a specific task and stops\n- Single source of truth: rely on `task_provider` config (Linear or file-based) for tasks\n- Task creation via ln-301 only; this skill never edits tasks directly\n- Test verification only runs when test task is Done\n- Language preservation in comments (EN\u002FRU)\n- **Agent code review is MANDATORY regardless of execution mode.** If ln-510 is invoked — it handles agent review (Phase 4\u002F8). If ln-510 is skipped or replaced with inline implementation — agent review MUST still be performed directly using `shared\u002Fagents\u002Fprompt_templates\u002Fmodes\u002Fcode.md` with at least 1 external agent and critical verification protocol. **MANDATORY READ:** Load `references\u002Fminimum_quality_checks.md` for non-negotiable checks.\n\n## Definition of Done\n- ln-510 quality checks: pass OR fix tasks created\n- Test task status checked; ln-520 invoked if needed\n- Test coverage verified (when test task Done)\n- Quality Score calculated; NFR validation completed\n- **Gate output format:**\n  ```yaml\n  gate: PASS | CONCERNS | FAIL | WAIVED\n  quality_score: {0-100}\n  nfr_validation:\n    security: PASS | CONCERNS | FAIL\n    performance: PASS | CONCERNS | FAIL\n    reliability: PASS | CONCERNS | FAIL\n    maintainability: PASS | CONCERNS | FAIL\n  issues: [{id: \"SEC-001\", severity: high|medium|low, finding: \"...\", action: \"...\"}]\n  ```\n- Story set to Done (PASS\u002FCONCERNS\u002FWAIVED) or fix tasks created (FAIL)\n- Branch finalized: committed, pushed to remote, worktree cleaned up (PASS\u002FCONCERNS\u002FWAIVED)\n- Root cause analysis recorded in architecture_health.md for every FAIL verdict\n- Comment with gate verdict posted\n\n## Phase 8: Meta-Analysis\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Fmeta_analysis_protocol.md`\n\nSkill type: `execution-orchestrator`. Run after all phases complete. Output to chat using the `execution-orchestrator` format.\n\n## Reference Files\n- **Tools config:** `shared\u002Freferences\u002Ftools_config_guide.md`\n- **Storage mode operations:** `shared\u002Freferences\u002Fstorage_mode_detection.md`\n- **Orchestrator lifecycle:** `shared\u002Freferences\u002Forchestrator_pattern.md`\n- **Quality coordinator:** `..\u002Fln-510-quality-coordinator\u002FSKILL.md`\n- **Test planner:** `..\u002Fln-520-test-planner\u002FSKILL.md`\n- **Risk-based testing:** `shared\u002Freferences\u002Frisk_based_testing_guide.md`\n- **Minimum quality checks:** `references\u002Fminimum_quality_checks.md`\n- **MANDATORY READ:** `shared\u002Freferences\u002Fgit_worktree_fallback.md`\n\n---\n**Version:** 7.0.0\n**Last Updated:** 2026-02-09\n","> **Paths:** File paths (`shared\u002F`, `references\u002F`, `..\u002Fln-*`) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.\n\n# Story Quality Gate\n\nThin orchestrator that coordinates quality checks and test planning, then determines final Story verdict.\n\n## Inputs\n\n| Input | Required | Source | Description |\n|-------|----------|--------|-------------|\n| `storyId` | Yes | args, git branch, kanban, user | Story to process |\n\n**Resolution:** Story Resolution Chain.\n**Status filter:** To Review\n\n## Purpose & Scope\n- Invoke ln-510-quality-coordinator for code quality checks\n- Invoke ln-520-test-planner for test planning (if needed)\n- Calculate Quality Score and NFR validation\n- Determine 4-level Gate verdict (PASS\u002FCONCERNS\u002FFAIL\u002FWAIVED)\n- Mark Story as Done or create fix tasks\n- Delegates ALL work — never runs checks directly\n\n## 4-Level Gate Model\n\n| Level | Meaning | Action |\n|-------|---------|--------|\n| **PASS** | All checks pass, no issues | Story -> Done |\n| **CONCERNS** | Minor issues, acceptable risk | Story -> Done with comment noting concerns |\n| **FAIL** | Blocking issues found | Create fix tasks, return to ln-400 |\n| **WAIVED** | Issues acknowledged by user | Story -> Done with waiver reason documented |\n\n**Verdict calculation:** `FAIL` if any check fails. `CONCERNS` if minor issues exist. `PASS` if all clean.\n\n## Quality Score\n\nFormula: `Quality Score = 100 - (20 x FAIL_count) - (10 x CONCERN_count)`\n\n| Score Range | Status | Action |\n|-------------|--------|--------|\n| 90-100 | Excellent | PASS |\n| 70-89 | Acceptable | CONCERNS (proceed with notes) |\n| 50-69 | Below threshold | FAIL (create fix tasks) |\n| \u003C50 | Critical | FAIL (urgent priority) |\n\n## NFR Validation\n\n| NFR | Checks | Issue Prefix |\n|-----|--------|--------------|\n| **Security** | Auth, input validation, secrets exposure | SEC- |\n| **Performance** | N+1 queries, caching, response times | PERF- |\n| **Maintainability** | DRY, SOLID, cyclomatic complexity, error handling | MNT- |\n\nAdditional prefixes: `TEST-` (coverage gaps), `ARCH-` (architecture), `DOC-` (documentation), `DEP-` (dependencies), `COV-` (AC coverage), `DB-` (database schema), `AC-` (AC validation)\n\n## When to Use\n- All implementation tasks in Story are Done\n- User requests quality gate for Story\n- ln-400-story-executor delegates quality check\n\n## Workflow\n\n### Phase 0: Tools Config\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Ftools_config_guide.md`, `shared\u002Freferences\u002Fstorage_mode_detection.md`, and `shared\u002Freferences\u002Finput_resolution_pattern.md`\n\nExtract: `task_provider` = Task Management → Provider (`linear` | `file`).\n\n### Phase 1: Discovery\n\n1) **Resolve storyId:** Run Story Resolution Chain per guide (status filter: [To Review]).\n2) Auto-discover team\u002Fconfig from `docs\u002Ftasks\u002Fkanban_board.md`\n3) Load Story + task metadata:\n   - IF `task_provider` = `linear`: `get_issue(storyId)` + `list_issues(parentId=storyId)`\n   - IF `task_provider` = `file`: `Read story.md` + `Glob(\"docs\u002Ftasks\u002Fepics\u002F*\u002Fstories\u002F*\u002Ftasks\u002F*.md\")`\n4) Detect test task status (exists? Done?)\n\n### Phase 2: Fast-Track Decision\n\nStories with high readiness (validated pre-execution) can skip expensive checks.\n\n```\nIF readiness_score available in CONTEXT:\n  IF readiness_score == 10:\n    fast_track = true\n  ELSE:\n    fast_track = false\nELSE:\n  fast_track = false    # No readiness data — full gate\n```\n\n**Fast-track matrix (readiness == 10):**\n\n| Component | Full Gate | Fast-Track | Why |\n|-----------|-----------|------------|-----|\n| ln-513 regression tests | RUN | RUN | Always critical, cheap |\n| Linters | RUN | RUN | Cheap, catches formatting |\n| Criteria Validation (3 checks) | RUN | RUN | Cheap, validates AC coverage |\n| ln-511 metrics + static analysis | RUN | **RUN** | **Catches complexity\u002FDRY\u002Fdead code that per-task review misses** |\n| ln-511 MCP Ref (OPT-, BP-, PERF-) | RUN | **SKIP** | Expensive external calls |\n| Inline agent review | RUN | **RUN (1 agent minimum)** | Catches logic\u002Falgorithm bugs that static analysis misses |\n| ln-520 test planning | RUN | **SKIP** | Redundant for pre-validated |\n| NFR validation | All dims | **Security only** | Perf\u002FMaintainability less critical |\n\n### Phase 3: Quality Checks (delegate to ln-510)\n\n1) **Invoke ln-510-quality-coordinator** via Skill tool\n   - Pass: Story ID (+ `--fast-track` flag if fast_track == true)\n   - Full: ln-510 runs: code quality (ln-511) -> criteria validation -> linters -> regression (ln-513)\n   - Fast-track: ln-510 runs: code metrics + static (ln-511 `--skip-mcp-ref`) -> criteria -> linters -> regression (ln-513) — skips MCP Ref\u002Fagent review\n2) **If ln-510 returns FAIL:**\n   - Create fix\u002Frefactor tasks via ln-301\n   - Stop — return to ln-400\n\n### Phase 4: Test Planning (delegate to ln-520)\n\n1) **IF fast_track: SKIP Phase 4 entirely** (proceed to Phase 5)\n2) Check test task status:\n   - **No test task** -> invoke ln-520-test-planner to create\n   - **Test task exists, not Done** -> report status, stop\n   - **Test task Done** -> proceed to Phase 5\n\n3) **Invoke ln-520-test-planner** via Skill tool (if needed)\n   - Pass: Story ID\n   - ln-520 runs: research (ln-521) -> manual testing (ln-522) -> auto test planning (ln-523)\n\n### Phase 5: Test Verification (after test task Done)\n\n1) Load test task:\n   - IF `task_provider` = `linear`: `get_issue(testTaskId)`\n   - IF `task_provider` = `file`: `Read` test task file from `docs\u002Ftasks\u002Fepics\u002F...\u002Ftasks\u002FT{NNN}-*.md`\n2) Verify limits and priority:\n   - Priority ≥15 scenarios covered\n   - Each test passes Usefulness Criteria (no numerical targets)\n   - Tests focus on business logic (no framework\u002FDB\u002Flibrary tests)\n3) Verify Story AC coverage by tests\n4) Check infra\u002Fdocs updates present\n\n### Phase 6: Final Verdict\n\n1) **Calculate Quality Score** (see formula above)\n2) **Run NFR checks** per dimensions table (fast_track: Security only; full: all dimensions)\n3) **Assign issue prefixes:** SEC-, PERF-, MNT-, TEST-, ARCH-, DOC-\n4) **Determine Gate verdict** per 4-Level Gate Model\n5) Post gate verdict comment:\n   - IF `task_provider` = `linear`: `create_comment({issueId: storyId, body: verdict_summary})`\n   - IF `task_provider` = `file`: `Write` comment to `docs\u002Ftasks\u002Fepics\u002F...\u002Fcomments\u002F{ISO-timestamp}.md`\n6) **If FAIL:** Record root cause analysis — classify each failure (missing_context | wrong_pattern | unclear_ac | doc_gap | test_gap). Append to `docs\u002Fproject\u002Farchitecture_health.md` under `## Root Cause Log` (create section if missing). Format: `| {date} | {story_id} | {issue_id} | {classification} | {action_taken} |`\n7) **Escaped defects (post-gate):** When bugs are discovered AFTER gate verdict (manual review, production, ln-310 mode=code_review), run Detection Efficacy Audit per `shared\u002Freferences\u002Fdetection_efficacy_audit.md`. Log results to `docs\u002Fproject\u002Farchitecture_health.md` under `## Escaped Defect Log`. Classifications: `algorithm_logic | performance_pattern | domain_specific | resource_bounds | encapsulation | data_structure | concurrency`.\n8) Update Story status:\n   - IF `task_provider` = `linear`: `save_issue({id: storyId, state: \"Done\"})` for PASS\u002FCONCERNS\u002FWAIVED; create fix tasks for FAIL\n   - IF `task_provider` = `file`: `Edit` `**Status:**` line to `Done` in story.md for PASS\u002FCONCERNS\u002FWAIVED; create fix task files for FAIL\n\n### Phase 7: Branch Finalization\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Fgit_worktree_fallback.md`\n\nRuns only when verdict is PASS, CONCERNS, or WAIVED. Consumes verified results from ln-510\u002Fln-513 — does NOT rerun checks.\n\n1. IF uncommitted changes exist → `git add -A && git commit -m \"{storyId}: {Story Title}\"`\n2. Push branch: `git push -u origin {branch}`\n3. Move Story + Tasks → Done (Linear or kanban)\n4. Report to chat + file: branch name, git stats (files changed, insertions, deletions), quality verdict\n5. Cleanup: `git worktree remove {worktree_dir}` (branch preserved on remote)\n\n**On FAIL verdict:** Skip Phase 7. Create fix tasks, return to ln-400.\n\n**TodoWrite format (mandatory):**\n```\n- Invoke ln-510-quality-coordinator (in_progress)\n- Check test task status (pending)\n- Invoke ln-520-test-planner (pending, if needed)\n- Verify test coverage (pending)\n- Calculate Quality Score + NFR (pending)\n- Determine verdict + update Story (pending)\n- Branch finalization (pending)\n```\n\n## Worker Invocation (MANDATORY)\n\n| Phase | Worker | Purpose |\n|-------|--------|---------|\n| 3 | ln-510-quality-coordinator | Code quality + criteria + linters + regression |\n| 4 | ln-520-test-planner | Research + manual testing + auto test planning |\n\n**Invocation:**\n```\nSkill(skill: \"ln-510-quality-coordinator\", args: \"{storyId}\")\nSkill(skill: \"ln-520-test-planner\", args: \"{storyId}\")\n```\n\n**Anti-Patterns:**\n- Running mypy, ruff, pytest directly instead of invoking ln-510\n- Running web searches or creating bash scripts instead of invoking ln-520\n- Marking steps as completed without invoking the actual skill\n- Any direct command execution that should be delegated\n\n## Critical Rules\n- Early-exit: any failure creates a specific task and stops\n- Single source of truth: rely on `task_provider` config (Linear or file-based) for tasks\n- Task creation via ln-301 only; this skill never edits tasks directly\n- Test verification only runs when test task is Done\n- Language preservation in comments (EN\u002FRU)\n- **Agent code review is MANDATORY regardless of execution mode.** If ln-510 is invoked — it handles agent review (Phase 4\u002F8). If ln-510 is skipped or replaced with inline implementation — agent review MUST still be performed directly using `shared\u002Fagents\u002Fprompt_templates\u002Fmodes\u002Fcode.md` with at least 1 external agent and critical verification protocol. **MANDATORY READ:** Load `references\u002Fminimum_quality_checks.md` for non-negotiable checks.\n\n## Definition of Done\n- ln-510 quality checks: pass OR fix tasks created\n- Test task status checked; ln-520 invoked if needed\n- Test coverage verified (when test task Done)\n- Quality Score calculated; NFR validation completed\n- **Gate output format:**\n  ```yaml\n  gate: PASS | CONCERNS | FAIL | WAIVED\n  quality_score: {0-100}\n  nfr_validation:\n    security: PASS | CONCERNS | FAIL\n    performance: PASS | CONCERNS | FAIL\n    reliability: PASS | CONCERNS | FAIL\n    maintainability: PASS | CONCERNS | FAIL\n  issues: [{id: \"SEC-001\", severity: high|medium|low, finding: \"...\", action: \"...\"}]\n  ```\n- Story set to Done (PASS\u002FCONCERNS\u002FWAIVED) or fix tasks created (FAIL)\n- Branch finalized: committed, pushed to remote, worktree cleaned up (PASS\u002FCONCERNS\u002FWAIVED)\n- Root cause analysis recorded in architecture_health.md for every FAIL verdict\n- Comment with gate verdict posted\n\n## Phase 8: Meta-Analysis\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Fmeta_analysis_protocol.md`\n\nSkill type: `execution-orchestrator`. Run after all phases complete. Output to chat using the `execution-orchestrator` format.\n\n## Reference Files\n- **Tools config:** `shared\u002Freferences\u002Ftools_config_guide.md`\n- **Storage mode operations:** `shared\u002Freferences\u002Fstorage_mode_detection.md`\n- **Orchestrator lifecycle:** `shared\u002Freferences\u002Forchestrator_pattern.md`\n- **Quality coordinator:** `..\u002Fln-510-quality-coordinator\u002FSKILL.md`\n- **Test planner:** `..\u002Fln-520-test-planner\u002FSKILL.md`\n- **Risk-based testing:** `shared\u002Freferences\u002Frisk_based_testing_guide.md`\n- **Minimum quality checks:** `references\u002Fminimum_quality_checks.md`\n- **MANDATORY READ:** `shared\u002Freferences\u002Fgit_worktree_fallback.md`\n\n---\n**Version:** 7.0.0\n**Last Updated:** 2026-02-09\n",{"name":5,"license":15,"description":7},"main","fa638b97a18ff6d9f26cf0eaf3dfa123531bcc87","organized-skills\u002Fln-500-story-quality-gate",1,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode","https:\u002F\u002Fgithub.com\u002Flevalencia","https:\u002F\u002Fmedium.com\u002F@luisevalencia","Microsoft MVP - Artificial Intelligence\r\nMachine Learning Enthusiast\r\n","2026-05-02 06:55:36",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add levalencia\u002Fagent-god-mode --skill ln-500-story-quality-gate",{"tool":47,"command":48},"bunx","bunx skills add levalencia\u002Fagent-god-mode --skill ln-500-story-quality-gate",{"tool":50,"command":51},"pnpm","pnpm dlx skills add levalencia\u002Fagent-god-mode --skill ln-500-story-quality-gate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-500-story-quality-gate\u002FSKILL.md",true,[55],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fminimum_quality_checks.md","REFERENCE","参考文档",2590,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-500-story-quality-gate\u002Freferences\u002Fminimum_quality_checks.md",[62,84,122,149,175,203],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":27},"01M6EM8ES5M9J4S8N78NJST0YC","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fzarr-python\u002FSKILL.md",[],[69,70,71,72,73,74,75,76,77,78,79,80,81,82,83],"python","zarr python","storage","integration","s3","gcs","cloud","dask","parallel","pipelines","arrays","numpy","scientific computing","scale","scientific",{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":103,"publishedAt":27},"01M6EM8AR6ZFKZ9YVW8TTG850Z","zabbix","Zabbix monitoring system automation via API and Python. Use when: (1) Managing hosts, templates, items, triggers, or host groups, (2) Automating monitoring configuration, (3) Sending data via Zabbix trapper\u002Fsender, (4) Querying historical data or events, (5) Bulk operations on Zabbix objects, (6) Maintenance window management, (7) User\u002Fpermission management","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fzabbix-api-skill\u002FSKILL.md",[90,95,98],{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":96,"categoryName":97,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":99,"categoryName":100,"taxonomyType":101,"taxonomyTypeDesc":102},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[86,69,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121],"automation","window management","monitoring","data","templates","api","system","operations","use","maintenance","objects","permission","bulk operations","triggers","host","events","via","bulk",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":27},"01M6EM6Q9JG846ECQY9A210A26","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fx-twitter-growth\u002FSKILL.md",[],[129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148],"twitter","x twitter growth","growth","competitive intelligence","search","analyzing","plan","marketing","web search","competitors","analyze","write","optimize","social","intelligence","viral","growth engine","mechanics","grow","competitive",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":27},"01M6EM3FQNPYNKPC4CV9TCVNGD","what-if-oracle","Run structured What-If scenario analysis with multi-branch possibility exploration. Use this skill when the user asks speculative questions like \"what if...\", \"what would happen if...\", \"what are the possibilities\", \"explore scenarios\", \"scenario analysis\", \"possibility space\", \"what could go wrong\", \"best case \u002F worst case\", \"risk analysis\", \"contingency planning\", \"strategic options\", or any question about uncertain futures. Also trigger when the user faces a fork-in-the-road decision, wants to stress-test an idea, or needs to think through consequences before committing.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fwhat-if-oracle\u002FSKILL.md",[],[156,157,158,159,160,161,162,163,164,165,166,167,112,168,169,170,171,172,173,174],"oracle","what if oracle","test","planning","ux","futures","risk","analysis","explore","decision","branch","question","exploration","options","stress-test","strategies","trigger","case","multi",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":184,"publishedAt":27},"01M6EM08C06RGDYCJ86HAPK0FF","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fvercel-react-best-practices\u002FSKILL.md",[181],{"categoryNo":182,"categoryName":183,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000009","前端开发",[185,186,187,188,189,190,191,192,193,194,195,196,197,107,198,199,200,201,202,117],"react","vercel react best practices","best practices","react best practices","vercel","writing","performance","components","react components","guidelines","tasks","code","Optimization","Next.js","refactoring","performance optimization","next","pages",{"skillNo":204,"name":205,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":207,"categories":208,"keywords":219,"publishedAt":27},"01M6EM00S13326QM08DTM94J6Z","venue-templates","Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fvenue-templates\u002FSKILL.md",[209,212,215,216],{"categoryNo":210,"categoryName":211,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":213,"categoryName":214,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":96,"categoryName":97,"taxonomyType":93,"taxonomyTypeDesc":94},{"categoryNo":217,"categoryName":218,"taxonomyType":101,"taxonomyTypeDesc":102},"01JBSEEDCAT000000000000036","内容创作者",[108,220,221,194,222,223,224,225,226,227,228,140,229,230,231,232,233,234,83,235],"venue templates","research","NeurIPS","ICML","LaTeX","science","Bash","access","read","edit","proposals","Academic","requirements","formatting","journal","chi"]