work-manager

Plugin work-manager from marketplace work-manager-marketplace in popoffvg/claude-plugin-work-manager. Commands read from the repo's manifest — 1 month ago.

Skills (11)

• work-done

  This skill should be used when the user says "work done", "done with work", "finish work", "mark complete", "close work". Mark work complete by updating the work note.

• work-help

  This skill should be used when the user says "work help", "how does work manager work", "work usage", "work commands", "what can work do". Shows available commands, workflow, and tips.

• work-implement

  This skill should be used when the current work phase is "implement". Provides the implementation workflow: reading the plan, executing tasks, running tests, saving results to _notes/impl-*.md, handling blockers, and checking completion criteria.

• work-install

  This skill should be used when the user says "work install", "install work manager", "setup work manager", "configure work manager", "work setup", "set up mise tasks", "install mise tasks". Guides through full work-manager setup: plugin installation, mise tasks, QMD, and environment configuration.

• work-plan

  This skill should be used when the current work phase is "plan". Provides the planning workflow: reading research notes, building acceptance criteria, creating ordered task lists with parallelization strategy, saving design decisions to _notes/plan-*.md, and transition to implement phase.

• work-pr

  This skill should be used when the user says "work pr", "create PRs", "open pull requests for my repos". Create PRs for all repos in the current workspace that have unpushed commits.

• work-recall

  This skill should be used when the user says "work recall", "where was I", "what was I working on", "resume work". Re-orient to current work — read notes, synthesize status, suggest next step.

• work-research

  This skill should be used when the current work phase is "research". Provides the research workflow: scope breakdown, codebase exploration, saving findings to _notes/research-*.md, and transition to plan phase.

• work-start

  This skill should be used when the user says "start work", "work start", "begin work", "initialize work". Start new work — detect branch, gather details, plan, save work note with hierarchical work notes structure.

• work-status

  This skill should be used when the user says "work status", "show my work", "what work am I on". Show raw work note for the current branch.

• work-update

  This skill should be used when the user says "update work", "log progress", "check off criteria", "update summary", "mark step done", "save knowledge", "document finding", "note decision". Update work note, manage work notes, and review notes structure.

Subagents (4)

• work-implementer

  Implement phase agent — writes code, runs tests, makes edits via subagents. Full tool access. Triggers when work-manager routes implement-phase work. NEVER spawn directly — only the work-manager router should delegate here. Requires _notes/_summary.md in cwd.

• work-manager

  Routes work commands to phase-specific agents. Triggers on start work, work recall, work done, work status, work update, work pr, where was I, resume work, catch me up, what's next. IMPORTANT — only use in directories with _notes/_summary.md or when user explicitly says "start work". If no work cont

• work-planner

  Plan phase agent — builds task list, writes acceptance criteria, designs implementation approach. Cannot edit source code or spawn code agents. Triggers when work-manager routes plan-phase work. NEVER spawn directly — only the work-manager router should delegate here. Requires _notes/_summary.md in

• work-researcher

  Research phase agent — explores codebase, gathers context, saves findings to _notes/. Cannot edit source code. Triggers when work-manager routes research-phase work. NEVER spawn directly — only the work-manager router should delegate here. Requires _notes/_summary.md in cwd.

Similar plugins