메뉴
Create a structured implementation plan for a new feature, refactor, or infrastructure change. Outputs a machine-readable markdown plan with phases, tasks, requirements, and testing criteria.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | create-implementation-plan |
| description | Create a structured implementation plan for a new feature, refactor, or infrastructure change. Outputs a machine-readable markdown plan with phases, tasks, requirements, and testing criteria. |
Create a detailed, actionable implementation plan for: ${input:PlanPurpose}
Save the output to: docs/features/<feature-name>/implementation-plan.md
---
goal: <Concise title>
version: 1.0
date_created: YYYY-MM-DD
status: 'Planned'
tags: [feature|refactor|infrastructure|migration]
---
# Implementation Plan: <Title>
## 1. Requirements & Constraints
- **REQ-001**: <Requirement>
- **SEC-001**: <Security requirement>
- **CON-001**: <Constraint>
## 2. Implementation Steps
### Phase 1: <Phase Name>
- GOAL-001: <What this phase achieves>
| Task | Description | File(s) | Completed |
|------|-------------|---------|-----------|
| TASK-001 | Description | `path/to/file.ts` | |
| TASK-002 | Description | `path/to/route.py` | |
### Phase 2: <Phase Name>
...
## 3. Architecture Diagram
```mermaid
graph TD
A[Frontend - Next.js] --> B[API Route]
B --> C[FastAPI Backend]
C --> D[(PostgreSQL)]
POST /api/v1/<resource> — description{ field: type }{ field: type }alembic revision --autogenerate -m "add_<feature>"| Test | Type | File |
|---|---|---|
| TEST-001 | pytest unit | backend/tests/test_<feature>.py |
| TEST-002 | Playwright E2E | frontend/tests/e2e/<feature>.spec.ts |
## Tips
- Keep tasks atomic — one task = one file or one function changed.
- Reference exact file paths (`src/app/api/...`, `backend/app/services/...`).
- For DB changes, always include the Alembic migration step.
- For new API endpoints, define the full request/response schema.
- Security requirements must be explicit (auth check, rate limit, input validation).
Source: [github/awesome-copilot — create-implementation-plan](https://github.com/github/awesome-copilot/tree/main/skills/create-implementation-plan)
When the user wants to review, edit, or improve existing website and marketing copy, especially requests like "review copy", "audit copy website", "polish landing page copy", "improve messaging", "tighten this text", or "copy feedback". Use this for existing copy in frontend/src and frontend/docs. For rewriting from scratch, hand off to copywriting. For structural conversion issues (section flow, CTA placement, friction), hand off to page-cro.
Generate a conventional commit message from staged/unstaged changes and automatically commit.
Create optimized multi-stage Dockerfiles for Next.js frontend and FastAPI backend. Smaller images, non-root user, healthcheck, pinned versions.
Generate a Playwright TypeScript E2E test for a given scenario. Navigates the app step-by-step, uses role-based locators, and saves the test in tests/e2e/.
PostgreSQL query optimization and schema review. Covers EXPLAIN ANALYZE, indexing strategy, JSONB, pagination, and security (parameterized queries).
Run pytest with coverage, identify uncovered lines, and iteratively add tests until 100% coverage is reached.