pbl/skills/lodge/SKILL.md
Use when the user asks to "lodge", "lodge specs", "archive", "clean up specs", "move to lodge", or wants to move completed spec directories out of the active workspace.
npx skillsauth add tim-hub/powerball lodgeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Move completed spec directories from .powerball/specs/ to .powerball/lodge/, after verifying specs and code are in sync.
.powerball/specs/ (match by name suffix after the date prefix)..powerball/specs/ and ask the user which to lodge..powerball/specs/ is empty, tell the user there's nothing to lodge and stop.Use /sync with the selected spec directory. This compares spec artifacts against actual code changes and surfaces any drift. If drift is found, the user decides whether to update specs, revert code, or accept drift before proceeding.
Only continue to Step 2 after sync-specs completes and any drift is resolved.
Before lodging, check both checklist.md and tasks.md in the selected spec directory:
Checklist check:
[x], proceed.[ ], warn the user which checkpoints are incomplete and ask whether to lodge anyway or go back and finish.checklist.md exists, proceed without warning.Unresolved review tasks check:
tasks.md for any [ ] tasks with "Review fix:" prefix — these are unresolved code review findings.tasks.md exists, proceed without warning..powerball/lodge/ if it doesn't exist..powerball/specs/YYYY-MM-DD-{{name}}/ to .powerball/lodge/YYYY-MM-DD-{{name}}/.Use /update-overview with the path to the lodged spec directory. This updates .powerball/lodge/overall.md with cumulative mermaid diagrams reflecting the work that was just lodged.
Only continue to Step 5 after update-overview completes.
Tell the user:
overall.md was created or updated (and which diagrams changed).powerball/specs/testing
Picks the right Kubernetes Deployment update strategy (RollingUpdate / Recreate / Blue-Green / Canary) for the situation. Use when configuring a new Deployment, changing rollout config, or deciding how to ship a risky change.
tools
Translates a markdown file to a target language, preserving structure. Use when the user needs a markdown file translated.
development
Translates text between any two languages while preserving source format. Use when the user needs to translate plain text, code, or markdown content.
testing
Generates written content — blog posts, social posts, emails, and marketing copy — matched to the project's existing voice. Use when the user needs written material.