بنقرة واحدة
ship
Use when all plan tasks are done and green to review, archive planning artifacts, and ask how to finish.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Use when all plan tasks are done and green to review, archive planning artifacts, and ask how to finish.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use at ship time to merge the spec into the living documentation, delete the staging spec and plan, and ask how to finish.
Use when taking over an existing codebase that has no living document. Produces a factual record of what already exists.
Use for standard or complex new work before coding or planning. Also handles vague goals — clarifies before designing.
Use at session start to learn how Praxis skills are invoked and why triage runs before every task.
Use when the goal is vague or vision-level and can't be defined well enough for design questions.
Use after design approval for milestone plans with executable acceptance.
| name | ship |
| description | Use when all plan tasks are done and green to review, archive planning artifacts, and ask how to finish. |
Gates — if any fail, stop here:
- [ ] in docs/staging/plans/YYYY-MM-DD-<topic>.md.review the whole diff.
Update docs/ROADMAP.md (if it exists):
[x].archive — merge spec into living document (except roadmap), delete staging spec and plan.
If user-visible, add to CHANGELOG Unreleased. Releases move it to a version.
Ask: commit / merge / PR / keep / discard.
On merge or PR: clean up worktree, delete local branch.
Roadmap has unchecked milestones? → plan next.
No push or PR without explicit user approval.