ctx

Plugin ctx from marketplace tdp-plugins in tdp1999/claude-code-ctx. Commands read from the repo's manifest — 14 days ago.

Skills (11)

• breakdown

  Decompose an epic into actionable task files in .context/tasks/. Triggers on "break down", "decompose", "create tasks from", "split into tasks", "breakdown". Use when an epic is ready and needs concrete work items. For standalone tasks without an epic, use /ctx:create-task.

• checklist

  The Owner's phase checklist (lanes S, M, L, a lookup table and Claude's playbook). Use it whenever an epic or task has a "Size: S|M|L" line, when another ctx skill (epic, breakdown, task, create-task) reaches a phase step, when the Owner mentions a checklist item by SN (for example "5.1c"), "lane",

• create-task

  Create a single task file from a brief description, independent of any epic. Triggers on "create task", "new task", "quick task", "add a task for", "I need to fix/add/update X". Use for one-off tasks, bug fixes, or small work that doesn't warrant a full epic. For epic-based tasks, use /ctx:breakdown

• domain

  Capture and maintain business logic, domain knowledge, flows, rules, and edge cases in plain text. Use when the project has business rules, user flows, domain concepts, or invariants that code alone cannot convey. Triggers on "domain", "business logic", "business rules", "flows", "domain model", or

• epic

  Plan a size-L feature as an epic (problem, questions, design, rules and examples) where the Owner writes the logic and Claude structures it and asks. Triggers on "epic", "plan feature", "new feature", "feature idea", "I want to build", "let's plan". Use when user describes a feature to implement, ev

• log-decision

  Record an architecture or technical decision as an ADR in decisions.md. Triggers on "log decision", "record decision", "ADR", "we decided to", "why did we choose", "architecture decision". Use when a non-trivial technical choice is made that future developers should understand.

• onboard

  Analyze an existing codebase and fill its context bank — vision, architecture, techstack — from what the code already says. Triggers on "onboard", "analyze this project", "document existing codebase", "join project", "extract architecture", "ctx setup". Use on any repo that already has code. For an

• progress

  Show project progress — pending, in-progress, blocked, and done tasks with domain coverage. Triggers on "progress", "status", "what's pending", "what's next", "show tasks", "how far along", "what needs to be done", "pick next task".

• start

  Set up a new project's context bank end to end — context folders, vision, architecture, techstack, and optionally a first epic broken into tasks. Triggers on "start project", "new project", "bootstrap", "init everything", "set up from scratch", "ctx setup". For a project that already has code, use /

• sync

  Reconcile progress.md with actual task files, archive done tasks, update epic statuses, check domain freshness. Triggers on "sync", "reconcile", "clean up tasks", "archive done", "update progress". Use after completing tasks or when progress.md seems stale.

• task

  Load a task file from .context/tasks/ and work on it, following acceptance criteria and patterns. Triggers on "work on task", "start task", "continue task", "task NNN", "pick up where I left off", "next task". Use when user wants to implement a specific task.

Similar plugins