plan-writing
Create actionable task plans with verification criteria
Complex development work often lacks clear structure and verification steps. This skill breaks down tasks into small, verifiable actions with explicit completion criteria.
์คํฌ ZIP ๋ค์ด๋ก๋
Claude์์ ์ ๋ก๋
์ค์ โ ๊ธฐ๋ฅ โ ์คํฌ โ ์คํฌ ์ ๋ก๋๋ก ์ด๋
ํ ๊ธ์ ์ผ๊ณ ์ฌ์ฉ ์์
ํ ์คํธํด ๋ณด๊ธฐ
"plan-writing" ์ฌ์ฉ ์ค์ ๋๋ค. Create a task plan for adding user authentication to my Next.js application.
์์ ๊ฒฐ๊ณผ:
- # User Authentication Implementation
- ## Goal
- Add secure user authentication using NextAuth with email/password and OAuth providers.
- ## Tasks
- - [ ] Install next-auth and bcrypt packages to Verify: npm install completes without errors
- - [ ] Create /api/auth/[...nextauth].ts route to Verify: Route file exists with NextAuth configuration
- - [ ] Add credentials provider to NextAuth config to Verify: Email/password login form submits successfully
- - [ ] Implement session management to Verify: Protected routes redirect unauthenticated users
- - [ ] Add OAuth providers (Google, GitHub) to Verify: OAuth login buttons appear and authenticate
- ## Done When
- - [ ] Users can register, login, logout, and access protected routes with session persistence
"plan-writing" ์ฌ์ฉ ์ค์ ๋๋ค. Plan a refactoring of our legacy jQuery codebase to React components.
์์ ๊ฒฐ๊ณผ:
- # jQuery to React Migration Plan
- ## Goal
- Incrementally migrate legacy jQuery components to React while maintaining functionality.
- ## Tasks
- - [ ] Audit existing jQuery components and document behavior to Verify: Spreadsheet listing all components with dependencies
- - [ ] Set up React build configuration alongside existing codebase to Verify: Both jQuery and React can coexist in same page
- - [ ] Migrate isolated utility components first (buttons, modals) to Verify: Migrated components pass visual regression tests
- - [ ] Create React wrapper for jQuery form handlers to Verify: Forms submit data correctly through React layer
- - [ ] Replace page-level jQuery logic with React components to Verify: All user flows complete without JavaScript errors
- ## Done When
- - [ ] All jQuery components replaced with React equivalents and jQuery dependency removed from package.json
๋ณด์ ๊ฐ์ฌ
์์ Static analyzer flagged 20 patterns (17 external_commands, 3 cryptographic) that are all FALSE POSITIVES. The SKILL.md file is documentation-only Markdown containing command examples in tables and code blocks, not executable code. Backticks are Markdown formatting, not shell execution. No cryptographic algorithms exist in the file. This is a safe planning skill that generates task breakdowns with verification criteria.
ํ์ง ์ ์
๋ง๋ค ์ ์๋ ๊ฒ
Feature Implementation Planning
Break down new feature development into discrete, testable tasks with clear dependencies and verification steps for systematic implementation.
Refactoring Project Organization
Structure large-scale code refactoring into manageable phases with verification criteria to ensure system stability throughout the process.
Bug Fix Documentation
Create clear action plans for complex bug fixes that span multiple files or require understanding intricate system interactions.
์ด ํ๋กฌํํธ๋ฅผ ์ฌ์ฉํด ๋ณด์ธ์
Create a task plan for adding user authentication to my Next.js application. Include setup, implementation, and verification steps.
I need to refactor our monolithic service into modular components. Create a phased plan that minimizes risk and allows incremental testing.
Users report intermittent 500 errors in our API. Create a systematic investigation plan with hypothesis testing and rollback steps.
Create a complete development plan for a new React + TypeScript project with testing, linting, and CI/CD configuration from scratch.
๋ชจ๋ฒ ์ฌ๋ก
- Start each plan with a single-sentence goal that clearly states what you are building or fixing.
- Limit plans to maximum 10 tasks - if work exceeds this, split into multiple focused plans.
- Always include specific verification criteria that anyone can follow to confirm task completion.
ํผํ๊ธฐ
- Creating plans with 50+ micro-tasks that become overwhelming and lose focus on outcomes.
- Writing generic tasks like 'Set up project' without specifying exact commands or expected outputs.
- Copy-pasting template plans without adapting to the specific project context and requirements.