plan
Plan
Overview
Write implementation plans for engineers who have zero project context. Document exactly what they need to know: files to touch, code to write, tests to update, docs to check, and how to verify the result. Give them the whole plan as bite-sized tasks.
Assume they are a skilled developer, but know almost nothing about our toolset or problem domain. Assume they don't know good test design very well; make the test intent, fixture setup, assertions, and failure coverage explicit. Plans must be standalone documents that do not rely on the prior chat.
Plan artifacts should be compact in prose and explicit in code. Explanations must be clear, but short; code snippets should carry most implementation detail.
Announce at start: "I'm using the plan skill to create the implementation plan."
More from tstelzer/skills
skill-creator
Guide for creating or updating simple, standalone skills with a single SKILL.md file
53discovery
Use for deep design discovery and problem understanding before planning or implementation. Trigger when the user wants to think deeply, build knowledge, surface edge-cases, ask many questions, or explore the problem space without producing plans or code; save a design artifact only when durable context is requested or clearly useful.
44effect-vitest
Testing Effect programs with vitest. Use when writing tests for effect-based code.
32effect
Explains basic effect usage and terms. Use when using effect in typescript.
31review-plan-implementation
Review code changes against a plan using the plan location and implementing git commit(s).
31effect-http-server
Explains how to define http servers with effect. Use only when a top-level server is, or needs to be written in effect.
30