agents-tasks

Plugin agents-tasks from marketplace agents-template in toderian/project_template. Commands read from the repo's manifest — 2 days ago.

Skills (24)

• add-task

  Create an area-prefixed task in docs/tasks_manager/_todos/ with a brief, phases, acceptance criteria, priority, optional spec/design sections, optional roadmap placement, and dates only when scheduling intent is explicit. Use when the user says \"add task\", \"create task\", \"file a task\", \"track

• align

  Check a proposed feature or change against PROJECT.md (vision, goals, scope, constraints) and report ALIGNED, NEEDS_CLARIFICATION, or OUT_OF_SCOPE. Use when the user wants to validate alignment before starting non-trivial work or before planning. Requires PROJECT.md at the repo root.

• artifacts-registry

  Where large, generated, encrypted, or reproducible artifacts are registered, and how to fetch, verify, add, and decrypt them via Git LFS and age. Use when adding a large/generated/encrypted file, fetching/verifying a registered artifact, or deciding if a file belongs in the registry.

• audit-todos

  Audit active task files against current repo state to find outdated, completed, obsolete, duplicated, or follow-up-ready work. Use when the user says \"audit todos\", \"audit tasks\", \"review active tasks\", or asks for periodic task backlog health checks.

• capture-idea

  Capture an idea into the inbox (docs/tasks_manager/_inbox/) as an I-NNN file with near-zero friction. Use whenever the user says \"capture\", \"add to inbox\", \"note this idea\", \"jot down\", or shares a feature/bug/idea they want recorded for later -- even if they don't explicitly ask to use a sk

• complete-task

  Complete or cancel an active task: reconcile progress, fill completion harvest/summary, optionally squash task commits, archive it, and sync ledgers. Use when the user says \"complete task\", \"finish task\", \"close task\", \"cancel task\", or asks to archive a done task.

• cross-repo-feature

  Capture a feature contract under docs/resources/<area>/contracts/<feature-slug>.md: repo responsibilities, API/schema/event/CLI/Docker boundaries, compatibility, rollout order, and verification. Use when the user says \"cross-repo feature\", \"feature contract\", or asks to coordinate a change acros

• cross-repo-pr-review

  Review multiple linked pull requests as one cross-repo feature: contracts, rollout order, compatibility, CI, and per-PR risks. Use when the user says \"cross-repo PR review\", \"review these PRs together\", \"multi-repo PRs\", or asks to validate PRs across repos.

• define-area

  Define or refresh docs/resources/<area>/ context for a domain/capability: participant repos, dependency graph, install modes, and known docs. Use when the user says \"define area\", \"index area\", \"map area\", or asks to establish cross-repo area knowledge.

• describe-component

  Generate or refresh a docs-primary component CONTEXT.md covering responsibility, public interface, dependencies, owned data, invariants, and tests. Use when the user wants to \"describe a component\", \"document this module/service\", map subsystem boundaries, or onboard/handoff code.

• distill-knowledge

  Distill raw documents, notes, exports, or pasted context into Markdown digests and durable docs/resources knowledge-base updates. Use when the user says \"distill knowledge\", \"process raw docs\", \"summarize these docs\", \"ingest docs\", or points to docs/resources/_inbox/ material.

• knowledge-base

  Canonical home for durable project knowledge: docs/resources/ source-of-truth split, discovery order, ADRs, runbooks, area summaries, digests, and generated-artifact naming. Use when deciding where durable knowledge belongs, writing an ADR/runbook, or when another skill points here for the knowledge

• map-system

  Create or refresh docs/resources/system-map.md as the status-aware repo, capability, flow, and boundary index. Use when the user asks to map the system, index working repos, refresh repo/capability architecture, or understand how repos fit together.

• prd-to-todos

  Extract actionable tasks from a PRD and create area-prefixed task files. Use when the user wants to convert a PRD into trackable tasks in docs/tasks_manager/_todos/.

• refresh-context

  Refresh the docs-primary knowledge base and detect stale architecture or domain context. Use when the user asks to \"refresh context\", \"reindex context\", \"update knowledge base\", or \"check context drift\".

• roadmap

  Maintain docs/tasks_manager/_roadmap.md -- the Urgent/Now/Next/Later/Someday ordering plus optional dated milestone headings. Use when the user wants to \"plan the roadmap\", \"what's next\", reprioritize/sequence work, schedule tasks, or refresh the roadmap. Distinct from per-change planning.

• simplify-task

  Reduce an existing task file to the smallest plan that still delivers it: merge phases that share files and tests, cut or defer speculative checklist items and criteria, drop empty optional sections, then rewrite the task after showing the before/after. Use when the user says \"simplify task\", \"th

• task-ledger

  Task/inbox file formats, ID reservation, area/repo registries, roadmap horizons, and the at ledger/reserve/repos-check tooling keeping docs/tasks_manager/ and docs/areas/ consistent. Use when creating, triaging, completing, or validating tasks/inbox ideas, or when another skill points here for the t

• tidy-repo

  Inventory scattered TODOs, loose docs, and orphan files, then propose a non-destructive migration into docs/tasks_manager and docs/resources. Use when the user says \"tidy this repo\", \"systematize\", \"clean up the mess\", or \"organize my tasks/docs\".

• triage-inbox

  Review captured inbox ideas (docs/tasks_manager/_inbox/) and promote worthwhile ones into full area-prefixed tasks, or drop them. Use when the user says \"triage inbox\", \"review the inbox\", \"process my ideas\", \"clear the inbox\", or wants to turn captured ideas into actionable tasks.

• ubiquitous-language

  Retrospectively harvest domain terms from the current conversation into docs/resources/CONTEXT.md, flagging ambiguities and proposing canonical terms. Use when the user wants to catch the glossary up after a discussion, define domain terms in bulk, harden terminology, or mentions \"domain model\" or

• verify-task

  Check that a finished task did what its task file says: re-run its tests fresh, verify each acceptance criterion goal-backward against the code (exists, substantive, wired), detect criteria that changed during the task, and get an independent spec-blind validation plus a whole-diff review. Use when

• wayfinder

  Plan an effort too big for one session as a map of decision tickets held in a single task file, and resolve them one at a time until the way to the destination is clear.

• workbook

  Layout, README shape, and script conventions for reusable workbook bundles under workbooks/<workbook-slug>/, including prompt-orchestration workbooks. Use when creating, organizing, or reviewing a workbook, or deciding whether a body of work belongs in workbooks/ versus docs/resources/.

Similar plugins