القائمة
Team-lead drives plan hardening after the current plan state already exists in repo docs.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Build a local, self-contained HTML A/B comparison viewer for two or more generated HTML variants (e.g. different template revisions, different data sets, before/after fixes), so a human can pick between panes side-by-side without any external hosting.
Reusable QA orchestration skill for GitHub PRs. Use for multi-pass QA, CI monitoring, and template-driven findings and final quality reports.
Generate a sprint status report for the current phase. Default is --table.
Generate and triage adversarial templates, var-files, and rendering inputs against sc-compose by coordinating bounded background agents, differential and metamorphic checks, minimization, and regression-test promotion. Use when trying to break a rendering subsystem, validating a risky change, hunting parser/validator/rendering edge cases, or turning a confirmed fuzz failure into a unit or CLI test.
Session initialization for the team-lead identity. Confirms identity and detects whether a full team restore is needed. Only run when ATM_IDENTITY=team-lead.
Repair Claude teammate routing after same-session compaction or resume when sc-compose still exists on disk and the saved leadSessionId still matches the current SESSION_ID, but ATM or teammate reachability is broken.
| name | plan-hardening |
| version | 1.4.0 |
| description | Team-lead drives plan hardening after the current plan state already exists in repo docs. |
| depends_on | {"codex-orchestration":"0.x"} |
Audience: team-lead only.
Use this only for phase-plan hardening before implementation starts or resumes.
team-lead routes the process but is not the authority for rewriting the
plandevelop before
startingSprint plan approved by:
plan-scope-reviewercritical-plan-reviewerquality-mgrAlways use:
.claude/skills/plan-hardening/sprint-planning-guidelines.md| # | Route to | Input required | Output expected | Read before executing |
|---|---|---|---|---|
| 1 | comp | vars file | step-1 fenced JSON | steps/step-1.md |
| 2 | plan-scope-reviewer (background) | context + step-1 JSON | step-2 fenced JSON | steps/step-2.md |
| 3 | comp | step-2 JSON | step-3 fenced JSON | steps/step-3.md |
| 4 | critical-plan-reviewer (background) | context + step-3 JSON | step-4 fenced JSON | steps/step-4.md |
| 5 | comp | step-4 JSON | step-5 fenced JSON | steps/step-5.md |
| 6 | quality-mgr | step-5 JSON + QA vars file | codex-orchestration plan-QA handoff | steps/step-6.md |
team-lead must keep a round table for every /plan-hardening run.
Minimum columns:
| Round | Step | Reviewer | reviewed_commit | status | blocking | important | minor | findings_hash | supersedes | Note |
|---|
Use the example in:
.claude/skills/plan-hardening/examples/plan-hardening-rounds.example.mdteam-lead only checks the top-level status and expected mode fields on
each fenced JSON response before advancingreviewed_commit changed or
findings_hash changedreviewed_commit and the same
findings_hash again, treat it as a stale replay and do not open a new
hardening roundFAIL three times without converging, escalate to
the user before continuing.claude/skills/plan-hardening/01-plan-scope-review.xml.j2.claude/skills/plan-hardening/02-sprint-scope-hardening.xml.j2.claude/skills/plan-hardening/03-consistency-hardening.xml.j2.claude/skills/plan-hardening/steps/step-1.md.claude/skills/plan-hardening/steps/step-2.md.claude/skills/plan-hardening/steps/step-3.md.claude/skills/plan-hardening/steps/step-4.md.claude/skills/plan-hardening/steps/step-5.md.claude/skills/plan-hardening/steps/step-6.md.claude/skills/plan-hardening/examples/plan-hardening-vars.example.json.claude/skills/plan-hardening/examples/plan-hardening-rounds.example.md.claude/skills/plan-hardening/examples/plan-hardening-qa-vars.example.json.claude/skills/plan-hardening/sprint-planning-guidelines.md