메뉴
Show the PARA workflow quick-reference guide with all available skills. Triggers on: "para help", "how do I use para", "what are the para commands", "show me para skills", "what can para do", "para overview".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Initialize the PARA workflow structure in the current project. Triggers on: "initialize PARA", "set up PARA workflow", "init para", "set up context directory", "initialize context structure", "start PARA in this project".
Decide whether the current request needs the PARA workflow or can be answered directly. Triggers on: "should I use PARA for this", "does this need a plan", "para check", "do I need to plan this", "is this a PARA task", "should I run para-plan".
Display the current PARA workflow state and suggest the next action. Triggers on: "what's the para status", "show workflow state", "para status", "where are we in the workflow", "what's our current task", "show me the context".
Generate a post-work summary document for the current PARA session. Triggers on: "summarize work", "write summary", "wrap up session", "para summarize", "create a summary", "summarize this phase", "summarize what we did".
Archive the current PARA context and create a clean slate for the next task. Triggers on: "archive context", "start fresh", "reset para context", "para archive", "archive and start over", "clean up context", "wrap up and archive".
Execute the active PARA plan by creating a branch and working through todos with spec-driven TDD. Triggers on: "execute the plan", "implement the plan", "para execute", "start implementing", "begin execution", "run the plan", "let's implement".
| name | para-help |
| description | Show the PARA workflow quick-reference guide with all available skills. Triggers on: "para help", "how do I use para", "what are the para commands", "show me para skills", "what can para do", "para overview". |
Display the PARA workflow quick-reference guide.
para-help
Display the following reference guide exactly:
Workflow: Research -> Plan -> Review Plan -> Execute -> Review PR -> Summarize -> Archive
Use PARA if the task results in git changes (features, bug fixes, refactoring, config, migrations, tests, complex debugging).
Skip PARA if the task is read-only or informational (questions, navigation, explanations).
| Skill | Purpose |
|---|---|
para-init | Initialize PARA structure in a project |
para-research [task] | Deep codebase exploration producing a research document |
para-plan [task] | Create a planning document (collaborative) |
para-review --plan|--pr | Staff+ independent agent review of plan or PR |
para-execute | Create branch, extract todos, start execution with spec-driven TDD |
para-workflow | Orchestrate full multi-phase cycle (execute -> PR -> review -> summarize -> merge) |
para-summarize | Generate post-work summary |
para-archive | Archive context and start fresh |
para-status | Check current workflow state |
para-check | Decision helper: should I use PARA for this? |
para-help | Show this reference |
para-research Add user authentication
-> Produces research doc
para-plan Add user authentication
-> Uses research doc, asks questions, creates plan
para-review --plan
-> Staff+ review of the plan
para-execute
-> AI implements (commits after each todo with TDD)
para-review --pr
-> Staff+ review of the implementation
para-summarize
para-archive
For large tasks, use phased plans:
para-plan Add payment system # (propose phased plan)
para-workflow --auto # Orchestrates all phases automatically
context/
├── context.md # Active session context
├── plans/ # YYYY-MM-DD-task-name.md
├── summaries/ # YYYY-MM-DD-task-name-summary.md
├── archives/ # YYYY-MM-DD-HHMM-context.md
├── data/ # Input/output files, specs, research docs
└── servers/ # MCP tool wrappers
para-status to see where you are in the workflowpara-check if unsure whether a task needs PARApara-research before planning non-trivial tasks~/.claude/CLAUDE.md