메뉴
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".
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".
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".
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".
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-check |
| description | 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". |
Decision helper to determine if the PARA workflow should be used for a given request.
para-check "Add user authentication to the API"
para-check "Where is the auth middleware defined?"
If no request is provided, ask: "What task would you like me to evaluate?"
Does this request require code or file changes?
├─ YES -> USE PARA (Research -> Plan -> Review -> Execute -> Review -> Summarize -> Archive)
└─ NO -> SKIP PARA
├─ About project code? -> Direct answer with file references
└─ General question? -> Standard response
Use PARA for tasks that result in git changes:
Skip PARA for read-only or informational tasks:
Display a short verdict with reasoning:
PARA Workflow Check
Request: "Add user authentication to the API"
✓ USE PARA WORKFLOW
Reason: This request requires code changes across multiple files.
Next: Run para-plan to create an implementation plan.
For skip cases:
PARA Workflow Check
Request: "Where is the auth middleware defined?"
✗ SKIP PARA -- Answer directly
Reason: This is a read-only question with no file changes needed.