claudecodex

tcw

Taxonomy · Capabilities · Work — skills that drive the tcw workflow.

10 on GitHubby Brian Cefaliv4.1.0Apache-2.0updated 9 days agoDeveloper Tools
/

Plugin tcw from marketplace tcw in brocef/TCW. Commands read from the repo's manifest — 9 days ago.

This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.

What it installs

Skills (14)

  • capabilities

    Drives `tcw capabilities` — the Capabilities axis of TCW (what a user can do). Use when a tcw work item has a product (user-facing) delta, or when coordinating capability wording across repos. The taxonomy axis is the `taxonomy` skill, the work axis the `work` skill.

  • commands-drive-work-to-completion

    Drive a TCW work item from wherever it is through implement, review and qa, to completed where the agent may record the qa verdict, or to qa for a person where it may not.

  • commands-pause-work

    Stop the work in hand gracefully, write down what resuming needs, and wait for the user.

  • commands-plan-work

    Plan a TCW work item from an existing item or the user's chat request, writing its request, spec and plan.

  • commands-process-inbox

    Decide on every arrival in a TCW project's work inbox, then write the request for each one accepted.

  • configure

    Changes how a project that already uses TCW is configured. Use when a user wants to set up or change the stages a project uses, the text or commands bound to a stage, hook limits, procedures, the Jira backend, documentation entries that track which documents a change must update, where a store lives

  • documentation-sync

    Use when completing a coding task and deciding whether documentation needs updating. Use when code changes have been made and you need to check if README, changelog, guides, or other docs should reflect those changes. Use when a project has documentation entries — from `tcw work docs`, or a `## Docu

  • extras-autonomous-work

    Use when asked to work TCW items autonomously, unattended, or "without asking me" — drives one or more items to completion via the commands-drive-work-to-completion skill, consulting read-only advisors in place of every human checkpoint (by default Codex and a read-only subagent on the strongest mod

  • extras-report

    Teaches a TCW user how to report a bug, issue, or suggestion back to the TCW project by filing a GitHub issue on the TCW repository, and hands them a ready-to-fill skeleton for each kind of report. Use when a user hits a `tcw` bug, wants to request a feature, or has feedback on TCW itself — not for

  • extras-triage-issues

    Triages the GitHub issues on **your own project's** repo and turns the ones worth acting on into `tcw work` items. Use when a user wants to check their project's GitHub issues, work through the issue backlog, or convert issues into tracked work. Most issues should not become work items, so triage de

  • setup

    Gets TCW working where it does not work yet. Use when a project does not use TCW yet, when the `tcw` CLI is missing, broken, or stale (not on PATH, `tcw --version` fails, or a plugin update left it behind), when an existing TCW project needs its stores or related projects on a new machine, when a TC

  • taxonomy

    Drives `tcw taxonomy` — the Taxonomy axis of TCW (the registered Vocabulary + Feature registry). Use when declaring or maintaining a project's registered language and features. The capabilities axis is the `capabilities` skill, the work axis the `work` skill.

  • work-create

    Turns an idea for a piece of work into a tracked TCW work item, or adds it to the item that already covers it, after checking the board, inbox arrivals included, and recording blockers, references and origin.

  • work

    Drives the `tcw work` change-tracking CLI — the Work axis of TCW (Taxonomy · Capabilities · Work). Use when planning, implementing, reviewing or testing a tcw work item; resuming one across sessions; deciding on an arrival in the inbox; splitting an item into child items; or making an epic's part in

Subagents (2)

  • backlog-auditor

    Read-only audit of ONE unfinished TCW work item against this project's audit-backlog procedure, which it reads from `tcw work procedure audit-backlog`, checking the item's claims against the code. Reports; never edits, never moves an item, never tags.

  • reviewer

    Read-only assessment for the TCW review stage — reads a work item's change against its spec, plan and capabilities.yaml, runs the project's checks, and recommends a verdict criterion by criterion. Never edits, never moves an item; the dispatching session writes the review round.

Hooks (1)

  • SessionStart

    "${CLAUDE_PLUGIN_ROOT}"/scripts/session_bootstrap.sh

View source on GitHub

Similar plugins

superpowers

claudecodex

Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques

15 skills · hooks

obra/superpowers 316,836

context7

claudecodex

Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.

1 MCP server

upstash/context7 64,709

Use Alibaba Open Code Review from local Codex.

2 skills

alibaba/open-code-review 50,068

slidev

claude

Claude Code skill for creating and presenting Slidev slidedecks

1 skill

slidevjs/slidev 49,452

gitnexus

claudecodex

Code intelligence powered by a knowledge graph. Provides execution flow tracing, blast radius analysis, and augmented search across your codebase.

12 skills · 1 MCP server · hooks

abhigyanpatwari/GitNexus 48,482

daisyui

claudecodex

daisyUI component library skill

7 skills

saadeghi/daisyui 42,821

Maintain tcw?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted