القائمة
Use when an approved implementation plan already exists (from craft, implement, or architect) and needs to be executed and tested. Combines develop + browser-test into a single pipeline.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | finalize |
| description | Use when an approved implementation plan already exists (from craft, implement, or architect) and needs to be executed and tested. Combines develop + browser-test into a single pipeline. |
Execute an already-approved plan and test the result. Use after planning has already produced a plan file.
Pipeline: Develop → Browser Test → Report
The user input is: $ARGUMENTS
.claude/plans/ (excluding archive/ and specs/)If no plan is found, suggest running craft-skills:architect or craft-skills:craft first.
Invoke craft-skills:develop with the plan.
After a successful build, invoke craft-skills:browser-test.
If the dev server isn't running, start it with npm run dev in the background before testing.
Summarize:
After reporting, offer craft-skills:finish to integrate the work (commit / PR / merge / cleanup).
Use when the user needs to plan and architect a new feature before implementation begins. This includes analyzing requirements, asking clarifying questions, and creating a detailed implementation plan aligned with the project's architecture. Invoke BEFORE any coding work starts.
Use when implementation + verification are complete and the work needs to be integrated — commit, open a PR, merge, or clean up the branch. The final step of the craft pipeline (after develop/test/report). Works in the current checkout; no worktree assumption.
Use when starting a new feature that needs thorough design exploration. This is the most comprehensive workflow: collaborative brainstorming with the user, then planning, then parallel agent development, then browser testing. Use for complex features, unclear requirements, or when the user wants to explore approaches before committing.
Post-develop visual regression + design-contract audit. Starts the dev server, captures screenshots of changed UI routes, and dispatches a Haiku-vision agent to compare the result against .claude/aesthetic-direction.md and the feature's ux-brief.md. Flags regressions before browser-test runs. Escalates to Sonnet or Opus only when Haiku flags issues.
Use when an approved implementation plan exists and is ready to be executed. Initializes shared state, dispatches parallel developer agents, performs integration review, and runs full verification (lint, tsc, format, build).
Generate or refresh .claude/reuse-index.md — a one-page inventory of the project's shared utilities, enums, hooks, and components that downstream implementer agents must consult before writing new code. Project-agnostic scan: no framework assumptions baked in. Invoke once per project (or when the shared surface changes meaningfully).