writing-plans
Writing Plans
Overview
Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.
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.
Announce at start: "I'm using the writing-plans skill to create the implementation plan."
Context: This should be run in a dedicated worktree (created by brainstorming skill).
Save plans to: docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md
- (User preferences for plan location override this default)
Scope Check
If the spec covers multiple independent subsystems, it should have been broken into sub-project specs during brainstorming. If it wasn't, suggest breaking this into separate plans — one per subsystem. Each plan should produce working, testable software on its own.
More from essentialsoft/agentskills
git-commit-push
create git commits and push code to GitHub safely. use when the user asks to commit, create branch, push changes, or prepare a pull request-ready commit with clear scope and verification.
12codebase-doc-writer
analyze an existing code repository and its current docs to generate and maintain system documentation, component maps, runtime flow indexes, module indexes, feature indexes, ai context, and known gaps. use when the user wants to understand how a program works, document architecture, trace implementation paths, prepare future maintenance context, or refresh project documentation after changes.
5git-commit
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping
2brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
1executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
1bio-ai-product-manager
help brainstorm ai chatbot and ai product ideas, analyze biology-related user needs, and draft product requirements documents, user stories, acceptance criteria, and api-aware feature requirements. use when the user wants product strategy help, prd drafting, requirement generation, roadmap thinking, or product discovery for applications and api services in biology or life science contexts.
1