.cursor/skills/plan-completion/SKILL.md
When you finish a plan file in active/, automatically move it to completed/. If it's the last plan in its set, move the whole set. Use when completing any plan under .llm/plans/active/.
npx skillsauth add podverse/podverse plan-completionInstall 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.
When you finish executing a plan file that lives in .llm/plans/active/, archive it (and
optionally its whole set) without asking the user.
active/ to completed/, preserving subdirectory structure.Example:
mv .llm/plans/active/dependabot-prs/plan-pr-107.md \
.llm/plans/completed/dependabot-prs/
A set is any group of plan files that belong together, for example:
migration-00-EXECUTION-ORDER.md, EXECUTION.md, or similar.migration-COPY-PASTA.md or *-COPY-PASTA.md..md files under one active/<feature>/ directory (e.g.
active/dependabot-prs/, active/bundle-optimizations/).If the plan you just finished is the last plan in that set (no other plan in the set remains in
active/), then move all plan files in that set from active/<feature>/ to
completed/<feature>/ in one go. Preserve the same directory structure under completed/.
How to tell it's the "last":
active/<feature>/ directory would have no
other plan files left (or only index/summary files that should move with the set).When moving a set, move the entire directory so that completed/<feature>/ contains the same
files that were under active/<feature>/.
Example (last plan in set — move whole directory):
mv .llm/plans/active/dependabot-prs .llm/plans/completed/
Always keep the same relative path under completed/ as under active/:
active/feature-name/01-part.md → completed/feature-name/01-part.mdactive/feature-name/subdir/02-part.md → completed/feature-name/subdir/02-part.mdIf a master plan or index (e.g. LLM-PLANS.md or a 00-master-plan.md) references the moved
plan(s) by path, update those references to point at completed/ instead of active/ where
appropriate.
| Situation | Action |
| ------------------------------- | ---------------------------------------------- |
| Finished one plan in a set | Move only that plan file to completed/ |
| Finished the last plan in a set | Move the whole set (directory) to completed/ |
| Don't ask | Archive automatically after the plan is done |
documentation
Per-job env validation and config patterns for the workers app. Use when adding or changing worker commands, touching workers startup validation, or documenting worker env vars.
development
Common patterns and examples for the podverse-web Next.js application
tools
Ensures client-side time displays use formatDateTimeAbbrev for localized, readable timestamps. Use when rendering dates/times in the UI or when the user mentions time formatting or local timezone display.
testing
--- name: podverse-testing-policy description: Skip test implementation unless the user explicitly asks. Use when a plan or task includes adding unit tests, a test phase, or "Phase 3: Tests". version: 1.0.0 --- # Testing policy — skip tests for now ## When to use - When a plan or task includes adding unit tests, a test phase, or "Phase 3: Tests". - When deciding whether to implement tests for a feature. ## Rules 1. **We are not concerning ourselves with tests at this time.** Skip test imp