Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From planning-with-files
Locks the active task_plan.md with a SHA-256 attestation, then hooks block plan injection if the file diverges from the recorded hash. Also supports --show and --clear flags.
How this command is triggered — by the user, by Claude, or both
Slash command
/planning-with-files:plan-attestThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
Run the plan attestation helper for the active plan.
Steps:
1. Resolve the active plan: prefer `${PLAN_ID}` env var, then `.planning/.active_plan`, then newest `.planning/<dir>/`, then legacy `./task_plan.md`.
2. Compute the SHA-256 of the resolved `task_plan.md`.
3. Write the hex digest to `.planning/<active-plan>/.attestation` (parallel-plan mode) or `./.plan-attestation` (legacy mode).
4. Confirm to the user with the short hash (first 12 hex chars) and the storage path.
Implementation:
- On Linux/macOS/Git Bash: `sh ${CLAUDE_PLUGIN_ROOT}/scripts/attest-plan.sh`
- On Windows PowerShell:...Run the plan attestation helper for the active plan.
Steps:
${PLAN_ID} env var, then .planning/.active_plan, then newest .planning/<dir>/, then legacy ./task_plan.md.task_plan.md..planning/<active-plan>/.attestation (parallel-plan mode) or ./.plan-attestation (legacy mode).Implementation:
sh ${CLAUDE_PLUGIN_ROOT}/scripts/attest-plan.sh& "$env:USERPROFILE\.claude\skills\planning-with-files\scripts\attest-plan.ps1"Flags:
--show — print the currently stored hash and where it lives.--clear — remove the attestation (re-open the plan to free editing).After running this command, every UserPromptSubmit and PreToolUse hook fire compares task_plan.md against the stored hash. If they diverge, the hook emits [PLAN TAMPERED — injection blocked] instead of feeding plan content into the model. Re-run /plan-attest whenever you intentionally edit and re-approve the plan.
npx claudepluginhub cscannellnexus/planning-with-files14plugins reuse this command
First indexed May 5, 2026
Showing the 6 earliest of 14 plugins
/plan-attestLocks the active task_plan.md with a SHA-256 attestation, then hooks block plan injection if the file diverges from the recorded hash. Also supports --show and --clear flags.
/implement_planImplements technical plans from a specified thoughts/shared/plans path, executing phases with verification, updating checkboxes, and pausing for manual review if needed.
/implement_planImplements approved technical plans from ./thoughts/shared/plans directory via phases with automated verification, manual pauses, and progress tracking.
/amend-planDiscusses amendments to plan.json via multi-turn conversation and applies confirmed changes by editing files and regenerating plan.md.
/planupdateQuickly syncs plan file with current codebase state: checks task completions, updates statuses and paths without executing changes.
/execute-planExecutes a PLAN.md file with per-task atomic commits, creates a SUMMARY.md, and updates project state. Supports autonomous, segmented, and decision-dependent execution strategies.