requirements-to-plan
Purpose
Turn a new requirement into an executable, code-backed implementation plan without making code changes.
Scope
This skill is for planning only.
- In scope: requirement clarification, design from requirements, impact analysis, implementation planning, risk and rollback planning, execution handoff.
- Out of scope: editing source code, running migrations, modifying infrastructure, making implementation commits.
Required Inputs
- Requirement statement
- Constraints and acceptance criteria (if available)
- Existing repository source tree
- Existing docs under
/docs(especially architecture and feature docs) - Root README and configuration files
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
2writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
1brainstorming
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
1