القائمة
Pipeline Step 1 — Pre-flight checks before plan hardening. Verifies git state, roadmap link, plan file, guardrails, and domain-specific instruction files.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Run a comprehensive code review across architecture, security, testing, naming, and patterns. Invokes relevant reviewer agents in sequence. Use before merging features or at the end of a phase. With --quorum, dispatches multi-model analysis for higher confidence.
Audit UI components for WCAG 2.2 compliance, semantic HTML, ARIA labels, keyboard navigation, color contrast, and responsive design.
Audit API endpoints for backward compatibility, versioning, OpenAPI compliance, pagination, rate limiting, and RFC 9457 error responses.
Review code for architecture violations: layer separation, sync-over-async, missing CancellationToken, improper DI. Use for PR reviews or code audits.
Fix a bug using TDD: reproduce with a failing test first, then implement the fix, then verify. Prevents regressions.
Review CI/CD pipelines for best practices: environment promotion, secrets management, rollback strategies, build caching, and deployment safety.
| name | planforge-step1-preflight-check |
| description | Pipeline Step 1 — Pre-flight checks before plan hardening. Verifies git state, roadmap link, plan file, guardrails, and domain-specific instruction files. |
| metadata | {"author":"plan-forge","source":".github/prompts/step1-preflight-check.prompt.md"} |
Pipeline: Step 1 of 5 (Session 1 — Plan Hardening)
When: Before hardening any*-PLAN.md
Model suggestion: Any model / Copilot Auto (10% token savings) — checklist verification works well on all models
Next Step:step2-harden-plan.prompt.md
Replace <YOUR-PLAN> with your plan filename (without path or .md extension).
Act as a PRE-FLIGHT CHECK AGENT for plan hardening.
Run these checks and report results. If any check fails, report the failure and do not proceed to Step 2.
GIT STATE — Run git pull origin main and git status.
Report: clean / dirty (list uncommitted files if dirty).
ROADMAP LINK — Read docs/plans/DEPLOYMENT-ROADMAP.md. Confirm the phase for exists with a one-line goal. Report: ✅ found (quote the goal) / ❌ missing.
PLAN FILE — Confirm docs/plans/.md exists and is non-empty. Report: ✅ exists (N lines) / ❌ not found.
CORE GUARDRAILS — Confirm these files exist and are non-empty:
4b. AGENTIC FILES — Check if prompt templates, agent definitions, and skills exist:
Output a summary table:
| Check | Result | Details |
|---|---|---|
| Git state | ✅/❌ | ... |
| Roadmap link | ✅/❌ | ... |
| Plan file | ✅/❌ | ... |
| Core guardrails | ✅/❌ | ... |
| Agentic files | ✅/⚠️ | ... |
| Domain guardrails | ✅/❌ | ... |
If ALL pass: "Pre-flight complete ✅ — proceed to Step 2 (Harden the Plan)" If ANY fail: "Pre-flight FAILED ❌" + list exactly what to fix.
Tip: For deeper diagnostics (environment tools, VS Code config, version currency, common problems), suggest running
pforge smith.
search_thoughts("preflight blockers", project: "TimeTracker", created_by: "copilot-vscode", type: "bug") — check if prior preflights failed for known reasonscapture_thought("Preflight blocker: <what failed and why>", project: "TimeTracker", created_by: "copilot-vscode", source: "plan-forge-step-1", type: "bug") — persist the blocker so it's caught earlier next timecapture_thought("Preflight passed: <key confirmations — branch strategy, resolved ambiguities>", project: "TimeTracker", created_by: "copilot-vscode", source: "plan-forge-step-1", type: "decision") — persist confirmations so next phase doesn't re-ask