Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/stella/folio --skill plan명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
SOC 직업 분류 기준
| name | plan |
| description | Create a new implementation plan in the repo's planning area. |
Create a new implementation plan in the repo's planning area.
$ARGUMENTS — A short slug for the plan, ideally kebab-case. If empty, derive a reasonable slug from the task.
Prefer this shared planning layout when the repo supports it:
.agents/ARCHITECTURE.md
.agents/GOALS.md
.agents/STATUS.md
.agents/plans/
If the repo uses a different planning area, adapt to it rather than creating duplicate systems.
Read planning context:
.agents/ARCHITECTURE.md if present.agents/GOALS.md if presentDetermine the plan location:
.agents/plans/Determine the next plan number:
ls .agents/plans/
Use the next sequential number when numbered plans are already in use. If the repo does not number plans, follow its established naming.
Research before writing:
Write the plan with this structure:
# Plan: [Feature Name]
Date: YYYY-MM-DD
## Goal
What are we building and why?
## Design Decisions
- **Decision**: Why this approach over alternatives.
## Scope
**In scope:**
- ...
**Out of scope:**
- ...
## Implementation
- `path/to/file` — what changes here
## Test Cases
What needs to be verified.
## Open Questions
Any unresolved decisions.
Plan well, do not over-specify:
Confirm before finalizing if the user is still shaping the task. If they asked you to just create the plan, go ahead and write it.