Menu
Use when the user asks Guardian to inspect project roadmap, milestone, plan, or ULW execution evidence.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use when the user asks Codex to drive the repo to the configured Guardian desired end state, such as commit, land, push, clean Guardian worktrees/branches, and safe hygiene cleanup.
Use when the user asks Codex to run Guardian workflows such as guardian status, guardian done, guardian finish, guardian recover, or worktree cleanup. Routes through the Codex Guardian adapter instead of raw git cleanup commands.
Use when the user asks Guardian to initialize, bootstrap, or write the repo-local Guardian config.
Use when the user says Guardian done, finish the job, complete the implementation, land and clean up, or asks Codex to run the normal Guardian completion workflow.
Use when the user asks Guardian to plan or apply the implementation-done cleanup workflow for redundant merged worktrees and branches.
Use when the user asks Guardian to delete exact files or directories through the safe path-deletion plan/apply flow.
| name | guardian-project-status |
| description | Use when the user asks Guardian to inspect project roadmap, milestone, plan, or ULW execution evidence. |
Run the Guardian Codex adapter instead of creating separate project notes or dashboards:
node <adapter-path> tool guardian_project_status '{}'
Use projectRoots only for explicit roots supplied by the user. Default output is read-only evidence. Use writeReport:true only when the user explicitly asks for the offline static project intelligence report at .git/opencode-guardian/project-report.html.
Keep Obsidian notes, copied status text, project registries, and repo-local status markdown out of this flow.