메뉴
Builds sorted rollup of next actions across all active opportunities using opportunity_report_next_steps_rollup template. Use when user asks for combined backlog, rollup next steps, or sorted pipeline todos by date.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Researches a company and writes a structured SWE-focused brief with source discipline, personal fit vs master.yaml, and Proceed/Pass-style conclusion. Use when the user asks for company research or employer due diligence.
End-to-end JD processing workflow: normalize raw JD, research company, score fit/gap, generate analysis reports, and import to opportunity tracker. One-shot skill that orchestrates the full analysis and opportunity import.
Reads a raw JD and produces a YAML snippet for opportunities.yaml plus optional jd_catalog.csv row. Use when adding a new pipeline opportunity from data/raw, ingesting a JD file, or bootstrapping opportunity id and next_action fields.
Produces next-steps markdown for a single opportunity from opportunities.yaml using opportunity_report_next_steps_one template. Use when the user asks for one-opportunity next actions, 24–72h moves, or snapshot for a given id.
Builds the full opportunity pipeline markdown report from opportunities.yaml using opportunity_report_tracking template. Use when the user asks for tracking list report, pipeline snapshot, or opportunity-tracking markdown output.
Updates one opportunity in opportunities.yaml (stage, next actions, close outcome, history). Use when the user changes pipeline stage, notes, next_action, or closes an opportunity by id.
| name | opportunity-report-next-steps-rollup |
| description | Builds sorted rollup of next actions across all active opportunities using opportunity_report_next_steps_rollup template. Use when user asks for combined backlog, rollup next steps, or sorted pipeline todos by date. |
Role: Assistant — career / opportunity tracking (see docs/AGENT_ROLES.md).
Context to load:
data/opportunities.yamltemplates/opportunity_report_next_steps_rollup.mdScope:
Task:
active with stage not Closed (unless user wants closed included).future_desired entries with next_action set.next_action_date ascending (empty dates last); secondary priority P0 → P1 → P2.opportunity_id for traceability.Output: Markdown for data/reports/pipeline/opportunity-next-steps-rollup-<YYYY-MM-DD>.md or paste-only.
Constraints:
data/ (gitignored), so real company/person names fine.next_action and next_action_date as recorded. Don't invent or extrapolate absent actions.next_action_date absent, sort row last, mark date cell "Not set". No date guessing.My inputs (collect, confirm, or ask):
next_action not stated in chat or memory: ask (or propose default and ask confirmation).<yes | no>