skills/plan-implementation/SKILL.md
Generates a structured, phased implementation plan for a new feature or codebase change, grounded in a research document. Use this skill whenever the user invokes /plan-implementation, asks to "make a plan", "write up a plan for this feature", "plan out these changes", "create an implementation plan", or is ready to plan before building. This is a pre-implementation planning skill — it should run after research and before coding. Trigger even if the user just says "let's plan this out" or "how should we approach building X". Do NOT trigger for debugging, code review, or requests to actually implement something. If the user is asking for a plan but doesn't have a research document, help them create one first.
npx skillsauth add aldengolab/lorist plan-implementationInstall 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.
Your job is to produce a structured, phased implementation plan for a feature or codebase change — grounded in evidence from the code, shaped through dialogue with the user, and written in enough detail to guide a subsequent implementation session.
You are not building anything. You are not reviewing code for quality. You are figuring out what to build, how to break it up, and what success looks like — and then writing it down precisely.
No implementation code in the plan. Describe changes in prose — what the code should do, not how to write it. Reference existing functions, types, and patterns by name, but never write code blocks containing implementation syntax (imports, function bodies, class definitions, config literals, etc.). Pseudo code is acceptable only when prose alone would be genuinely ambiguous. The implementation session will write the code; the plan's job is to make the intent unambiguous.
This skill is conversational. You move through distinct stages before writing anything. Don't skip ahead.
./research/; read all mentioned files fully../plan/[YYYY-MM-DD]-[codebase_snakecase]-plan.md.For detailed stage instructions and the output document template, read reference files when you reach that stage:
Read skills/plan-implementation/references/stage-instructions.mdRead skills/plan-implementation/references/output-format.mddevelopment
Build a UEFI Secure Boot PXE netboot server for Ubuntu autoinstall. Use when: designing or implementing network boot infrastructure for automated Ubuntu provisioning with Secure Boot enabled. Covers the complete chain: signed shim+GRUB selection, TFTP layout, kernel parameters, autoinstall config requirements, and post-install bootstrapping scripts. Also applicable when debugging an existing PXE setup that uses the wrong GRUB binary or config paths.
development
Design pattern for running a persistent PXE/TFTP server that safely coexists with already-installed nodes. Use when: building PXE infrastructure that should stay always-on, designing automated bare-metal provisioning in GitOps/Kubernetes environments, or any PXE setup where UEFI boot order has network boot first. Eliminates boot loops without requiring UEFI firmware changes.
development
This skill governs all prose output — Claude's own responses, documentation, PR descriptions, commit messages, README content, comments, and any text the user asks to draft or edit. It should also be used when the user asks to "review my writing", "edit this for clarity", "make this clearer", "simplify this text", "rewrite this", "check my prose", "tighten this up", or "make this more concise". Based on George Orwell's "Politics and the English Language" (1946).
development
Debug Kubernetes pods using hostNetwork: true that crash with "Address already in use" or "failed to create listening socket for port N". Use when: (1) a hostNetwork pod container is in CrashLoopBackOff and logs show a port bind failure, (2) the port works fine in non-hostNetwork pods but fails with hostNetwork, (3) you need to identify which host-level process holds a port from within Kubernetes (no SSH). Covers /proc/net/udp inspection and kubectl debug node with nsenter.