메뉴
Aggregate all open tasks across the vault (personal, project-specific, deadline-driven) into one prioritized list. Use when the user asks "what do I need to do," "what's on my plate," "to-do list," or /task-list.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Log a vault change (note created/edited/deleted) to a running daily changelog note. After any write to the vault, ask the user "should this be logged?" and run this skill on confirmation. Also runs directly when the user says /changelog.
Update a project's README and the relevant vault notes (overview / module map) after a meaningful code change — new feature, new file, new module, or an architectural decision. Should trigger on its own once a coding task is finished, without the user having to ask — skip it for trivial (typo/formatting) changes. Also runs manually when the user says "update the docs" or "document this."
Update "where we left off" tracking for {PROJECT} when a milestone or unit of work closes. Updates Status.md (active milestone + next concrete action) and Milestone_Log.md (chronological record); touches Goal.md/Decisions.md if needed. Called by project-orchestrator at the end of every milestone; also used directly when the user says "log this milestone" or "update status."
Design phase for {PROJECT} — data model, module boundaries, API contract, access control, and any multi-tenancy/security design, before code is written. Called by project-orchestrator before implementation; also used directly when the user says "design {PROJECT}'s X module."
Implementation phase for {PROJECT} — builds the actual code for a module or vertical slice against an existing design. Called by project-orchestrator once a design exists; also used directly when the user says "implement {PROJECT}'s X module."
Main orchestrator for building {PROJECT}. Tracks cross-session continuity, reads "where we left off," routes to the correct phase sub-skill, and runs autonomously. Use when the user says "continue {PROJECT}," "work on {PROJECT}," "{PROJECT} where did we leave off," or /project-orchestrator. This is for the BUILD side of {PROJECT} — not for unrelated day-to-day tasks about it.
| name | task-list |
| description | Aggregate all open tasks across the vault (personal, project-specific, deadline-driven) into one prioritized list. Use when the user asks "what do I need to do," "what's on my plate," "to-do list," or /task-list. |
Tasks tend to live scattered across several source files (a personal to-do note, per-project status files, a deadlines note). This skill's job is to read all of them and produce one view, not to be the single place tasks are written.
Read each known task source in the vault (adapt this list to your own vault — e.g. a general to-do note, each active project's status file, a deadlines note).
Combine everything into one list, ordered:
Tag each item with which source file it came from, so the user can go fix it at the source rather than in this aggregated view.
A flat prioritized list, source-tagged, is usually more useful than grouping by project — the point of aggregation is to answer "what's most urgent right now" across everything at once.
If the user adds or completes a task during this conversation, write the change to its source file, not to this skill's output — the aggregated list is always regenerated, never the source of truth itself.
