메뉴
Create and maintain one-page project briefs (goal, success criteria, constraints, stack, status, next actions). Use when starting a new project, updating a project's status, or asked 'what's the status of X?'
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Double-model verification gate before declaring a build/research/refactor "done". Runs a fresh Anthropic (Claude) review AND an independent OpenAI/Azure critic against the stated goal + criteria, then reconciles. Use before announcing completion of medium/major builds, refactors, major fixes, research deliverables, frontend work, or trade-decision rigor — and on demand via /verify. Skip for small Q&A and trivial edits.
Record and retrieve Architecture Decision Records — log a decision's context, options, rationale, and tradeoffs, then list/search them. Use when making a non-trivial design or architecture decision, choosing between tools/approaches, or asked 'why did we do it this way?'
Queue an external action (Telegram message, shell command, GitHub comment, PR merge, file write) for the user's explicit approval before it runs. Use when you want to take an outward-facing or irreversible action that needs sign-off first.
Run a structured multi-position debate over an analytical question, spawning sub-agents to argue each option and counter confirmation bias. Use when comparing options or tradeoffs — 'which is better', 'should we', 'what's the risk', 'evaluate', 'compare options'.
Ingest documents (URLs, local files, PDFs) into a searchable local knowledge base and query stored knowledge. Use when ingesting or storing documents, searching previously stored knowledge, or building research context.
Collect macro market and economic-calendar data (yfinance + FairEconomy API) into a SQLite DB and generate a formatted macro briefing for Telegram. Use when producing a macro/markets briefing or collecting macro market data.
| name | project-brief |
| description | Create and maintain one-page project briefs (goal, success criteria, constraints, stack, status, next actions). Use when starting a new project, updating a project's status, or asked 'what's the status of X?' |
| category | productivity |
| maturity | stable |
| tags | ["project-status","brief","goals","blockers","tracking"] |
Use when: starting a new project, updating a project's status, or when the user asks "what's the status of X?"
node ${PROJECT_BRIEF_HOME:-$HOME/projects/project-brief}/brief.cjs new
--project
--goal "What this project does and why"
--success "criterion 1,criterion 2,criterion 3"
--constraints "constraint 1,constraint 2"
--stack "tech1,tech2"
--status "Active"
--next "first next action,second next action"
node ${PROJECT_BRIEF_HOME:-$HOME/projects/project-brief}/brief.cjs list
node ${PROJECT_BRIEF_HOME:-$HOME/projects/project-brief}/brief.cjs status
node ${PROJECT_BRIEF_HOME:-$HOME/projects/project-brief}/brief.cjs view
node ${PROJECT_BRIEF_HOME:-$HOME/projects/project-brief}/brief.cjs update --status "Complete" node ${PROJECT_BRIEF_HOME:-$HOME/projects/project-brief}/brief.cjs update --add-next "New action item" node ${PROJECT_BRIEF_HOME:-$HOME/projects/project-brief}/brief.cjs update --check "Success criterion text" node ${PROJECT_BRIEF_HOME:-$HOME/projects/project-brief}/brief.cjs update --add-history "What changed today" node ${PROJECT_BRIEF_HOME:-$HOME/projects/project-brief}/brief.cjs update --add-blocker "What's blocking" node ${PROJECT_BRIEF_HOME:-$HOME/projects/project-brief}/brief.cjs update --resolve-blocker "What's blocking" node ${PROJECT_BRIEF_HOME:-$HOME/projects/project-brief}/brief.cjs update --current-status "One-liner on current state"
~/projects//BRIEF.md
