Tsh Creating Implementation Plans
Productivitytsh-creating-implementation-plansTsh Creating Implementation Plans is an Agent Skill for productivity published in the TheSoftwareHouse/copilot-collections repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Creates implementation plan documents (*.plan.md) that break a designed solution into phases and verifiable tasks. Owns the plan template (plan.example.md), plan structure rules, and task definition-of-done rules. Use when authoring, revising, or structuring an implementation plan for any feature or task.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/TheSoftwareHouse/copilot-collections/blob/HEAD/.github/skills/tsh-creating-implementation-plans/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/tsh-creating-implementation-plans, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Creating Implementation Plans
This skill turns a designed solution into a phased, verifiable implementation plan document.
Plan Creation Process
Before drafting, read ./plan.example.md in full first — it is the canonical structure every plan must follow. Knowing the required sections up front tells you which fields you must research, discover, or design (for example Technical Context, Current Implementation Analysis, and Security Considerations) before you begin, so you gather the right information deliberately rather than backfilling it later.
- Confirm inputs: a designed solution, typically from
tsh-architecture-designing, plus task research and context. Do not design the solution here; this skill structures an already-designed solution into a plan. - Define the Wildly Important Goal and the plan description.
- Divide the work into small phases. Each phase must have a Goal, a Description, a
**Verification:**field listing the exact fast-running checks to run after the phase completes, and a list of tasks with checkboxes to mark finished tasks later. Keep phase verification reviewer-verifiable and limited to fast checks such as unit tests, integration tests, static code analysis, linters, formatting checks, and project build. Source these checks from the plan's Technical Context → Tech Stack / Testing Patterns rather than assuming Node/npm. - Define each task. Each task must have a Description, a
**Files:**field, and a Definition of Done as a checkbox list. Phase Description states the broader why for reviewers and implementors. Task Description should use a near-imperative form that names the files and the behavior to change. The**Files:**field must name every file the task will touch and label each one withcreate,modify, orreuse. If a file was produced or last touched by an earlier task in the same plan, include an inline back-reference such as(modify — created in Task 1.1); if a file is created and consumed within the same task, no back-reference is needed. Tasks may also include an optional**Stop Rule:**sentence nearCluesthat tells the implementor to stop, report, and avoid improvising if the task cannot proceed safely or an expected seam is missing; do not turn this into a formal dependency graph or aDepends on:field. Optional Clues should still help the implementor with file paths, line ranges, reference patterns, and gotchas. - Add the mandatory cross-cutting tasks required by the plan rules.
- Save the plan as a document following the
./plan.example.mdtemplate. Do not add or remove any sections from the template. Follow the structure and naming conventions strictly.
Connected Skills
tsh-architecture-designing- designs the solution this skill turns into a plantsh-implementation-gap-analysing- verifies what was already implemented before planning new worktsh-technical-context-discovering- populates the plan's Technical Context section