Automated summary
Turns a vague feature request into a structured implementation plan with goals, constraints, and acceptance criteria.
Strengths
- Clarifies scope and non-goals to prevent scope creep
- Identifies risks and technical dependencies early
- Produces testable acceptance criteria
- Documents open questions for design iteration
Limitations
- Relies on the quality of the initial request
- May be overly formal for trivial changes
- Does not replace a full impact analysis
Use this skill before implementing a complex or ambiguous feature to align the team on a shared vision.
Avoid this skill for simple bugs or maintenance tasks that don't require upfront planning.
Security analysis
SafeThe skill is purely declarative, guiding the AI to produce a textual plan without any tool execution, file access, or network activity. No security risks are present.
No concerns found
How this analysis is madeExamples
Plan the implementation for adding OAuth2 login to our web app. The feature should support Google and GitHub as providers, and store tokens securely. Existing users can still use email/password.I want to add a dark mode toggle to the settings page. It should apply system-wide and respect the OS preference by default. Create an implementation plan.Plan a feature: users receive email notifications for new messages. Notifications can be paused per conversation. We use SendGrid. Generate the plan with goals, non-goals, and risks.name: feature-planner description: Turn a feature request into an implementation-ready plan with scope, constraints, acceptance criteria, and risks.
Goal
Convert an ambiguous feature idea into a concrete plan before implementation.
Workflow
- Restate the target outcome in one paragraph.
- Separate goals from non-goals.
- Identify affected user flows, entry points, and likely files.
- List constraints, dependencies, and migration concerns.
- Produce acceptance criteria.
- Leave unresolved questions as explicit open items.
Output format
Outcome
Goals
Non-goals
Affected areas
Constraints and risks
Acceptance criteria
Open questions
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/feature-planner-mrwakft2/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/feature-planner-mrwakft2' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/feature-planner-mrwakft2/download' --output '.skill-downloads/feature-planner-mrwakft2/SKILL.md.part' && mv '.skill-downloads/feature-planner-mrwakft2/SKILL.md.part' '.skill-downloads/feature-planner-mrwakft2/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/feature-planner-mrwakft2/SKILL.md' && test -s '.skill-downloads/feature-planner-mrwakft2/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/feature-planner' && cp -R '.skill-downloads/feature-planner-mrwakft2' '.claude/skills/feature-planner'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/feature-planner-mrwakft2'openskills read 'feature-planner-mrwakft2'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/feature-planner-mrwakft2/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.