How do I install the Planning Features skill?

Run npx skillmds add majiayu000/planning-features in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Planning Features safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Planning Features?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Planning Features free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Planning Features?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Planning Features by majiayu000 — Agent Skill

Name: Planning Features
Rating: 4.5 (4 reviews)
Author: majiayu000

Planning Features

Plan and document features before implementation using project templates. Use when planning new features, creating architecture docs, or when user mentions "plan", "design", "architect", "feature plan", "implementation plan", or "before coding".

majiayu000 a304120 2 files · 2.5 KB Updated Sep 9, 2026 567 repo stars

File contents

Feature Planning

Create structured planning documents before implementation.

When to Plan

Create a plan for:

New features with multiple components
Changes affecting multiple files
Backend + frontend integration work
Architecture decisions
Refactoring efforts

Skip planning for:

Single-file bug fixes
Minor styling tweaks
Documentation updates

Planning Workflow

- [ ] Step 1: Clarify requirements with user
- [ ] Step 2: Research existing patterns in codebase
- [ ] Step 3: Identify affected files/components
- [ ] Step 4: Create planning document
- [ ] Step 5: Get user approval before implementing

Plan Location

.github/plans/feature-name-plan.md

Use kebab-case for filenames.

Plan Template

See TEMPLATE.md for the full template.

Quick Plan Structure

# Feature: [Name]
**Date**: YYYY-MM-DD
**Status**: Planning

## Objective
What problem does this solve?

## Technical Approach
- Architecture decisions
- Components to create/modify
- API endpoints needed

## Implementation Steps
1. [Step with file path]
2. [Step with file path]

## Testing Strategy
- Unit tests needed
- Manual testing checklist

## Checklist
- [ ] Audio integration considered
- [ ] Responsive design planned
- [ ] Error handling defined
- [ ] No new dependencies (or approval obtained)

Architecture Considerations

Always address:

Aspect	Question
Audio	What sounds should play?
Responsive	Mobile behavior at 768px?
State	Local state or context?
Data	tRPC query or static?
Auth	Protected or public?
Performance	Memoization needed?

After Implementation

Create completion doc at:

.github/documentation/feature-name-complete.md

---name: planning-featuresdescription: Plan and document features before implementation using project templates. Use when planning new features, creating architecture docs, or when user mentions "plan", "design", "architect", "feature plan", "implementation plan", or "before coding".--- # Feature Planning Create structured planning documents before implementation. ## When to Plan Create a plan for: - New features with multiple components - Changes affecting multiple files - Backend + frontend integration work - Architecture decisions - Refactoring efforts Skip planning for: - Single-file bug fixes - Minor styling tweaks - Documentation updates ## Planning Workflow ``` - [ ] Step 1: Clarify requirements with user - [ ] Step 2: Research existing patterns in codebase - [ ] Step 3: Identify affected files/components - [ ] Step 4: Create planning document - [ ] Step 5: Get user approval before implementing ``` ## Plan Location ``` .github/plans/feature-name-plan.md ``` Use kebab-case for filenames. ## Plan Template See [TEMPLATE.md](TEMPLATE.md) for the full template. ## Quick Plan Structure ```markdown # Feature: [Name] **Date**: YYYY-MM-DD **Status**: Planning ## Objective What problem does this solve? ## Technical Approach - Architecture decisions - Components to create/modify - API endpoints needed ## Implementation Steps 1. [Step with file path] 2. [Step with file path] ## Testing Strategy - Unit tests needed - Manual testing checklist ## Checklist - [ ] Audio integration considered - [ ] Responsive design planned - [ ] Error handling defined - [ ] No new dependencies (or approval obtained) ``` ## Architecture Considerations Always address: | Aspect | Question | |--------|----------| | Audio | What sounds should play? | | Responsive | Mobile behavior at 768px? | | State | Local state or context? | | Data | tRPC query or static? | | Auth | Protected or public? | | Performance | Memoization needed? | ## After Implementation Create completion doc at: ``` .github/documentation/feature-name-complete.md ```

Frequently asked questions