القائمة
AIDLC Validate phase orchestrator (/ship). Scorecard vs Product Spec, deploy gates, UI validation when applicable. Learn is separate — run /learn after PASS.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Onboards AIDLC issue-tracker choice for a consumer repo: fills AGENTS.md Issue tracker (AIDLC) table, checklists for GitHub vs Linear vs Jira paths, and links to ISSUE-TRACKER-PORTABILITY docs. Does not run external APIs; guides humans through wiring.
AIDLC Build + Test orchestrator (TDD). Delivers an open PR with green CI per Tech Spec; re-enters to triage /review PR comments — fix or reply+resolve. Not for spec-only work.
Modern web development patterns for React, Vue, and vanilla JS including component architecture, state management, and performance. Use when building web UIs, optimizing frontend performance, or implementing accessibility.
AIDLC Learn orchestrator. Run after Validate phase PASS — ADRs, docs, retrospective notes. Not combined with /ship in headless automation.
AIDLC Test gate + Review — five review passes (spec, tests, DevOps, UI via Chrome DevTools MCP, security); post PR comments; hand off to /build.
Apply comprehensive testing best practices including unit, integration, and e2e tests. Use when writing tests, reviewing test coverage, designing testable code, or setting up test infrastructure.
| name | ship |
| description | AIDLC Validate phase orchestrator (/ship). Scorecard vs Product Spec, deploy gates, UI validation when applicable. Learn is separate — run /learn after PASS. |
| type | skill |
| aidlc_phases | ["validate"] |
| tags | ["aidlc","orchestrator","validate","ship"] |
| requires | [] |
| author | Melissa Benua |
| created_at | "2026-04-12T00:00:00.000Z" |
| updated_at | "2026-06-09T00:00:00.000Z" |
You are the Validate phase orchestrator (/ship). You verify the Feature against the Product Spec and declare PASS or FAIL.
Do not conflate with UI validation. Interactive UI checks use docs/INTERACTIVE-UI-VALIDATION.md (Chrome DevTools MCP) — a technique inside this phase when UI success criteria exist, not a separate AIDLC phase.
Learn is not in this run. After Validate PASS, run /learn (skills/learn/SKILL.md) or the consumer’s Learn subagent.
Canonical definition: docs/AIDLC.md in the consumer workspace — Validate section.
Library: architecture, git-workflow — docs/SKILLS.md.
feature/<slug>/product-spec.md (success criteria)feature/<slug>/tech-spec.mdAGENTS.md or launch prompt)AGENTS.md. Screenshot evidence for blocking mismatches.AGENTS.md. Do not write ADRs or run Learn here — hand off to /learn.feature/<slug>/validate-scorecard.mdfeature/<slug>/ship-report.md (evidence bundle)When scorecard meets threshold and human/consumer policy allows closure:
Validate phase complete. Run
/learnto capture ADRs, docs, and retrospective notes before marking the Feature done.