TStack — a Claude Code Plugin

TStack is a seven-skill Claude Code plugin that takes you from a rough product idea to a fully documented, milestone-sequenced, built project. Each stage is a skill that auto-triggers based on what you say, reads its input artifact from disk, produces its output, and hands off to the next.

Replaces a previous paste-the-guide-into-each-session workflow with a chain of skills that activate automatically and remember the state of your project on disk.

The Lifecycle

flowchart LR
  A["**tstack-discover**<br/>rough idea → business-brief.md"]
  B["**tstack-product**<br/>brief → PRODUCT.md"]
  C["**tstack-architect**<br/>PRODUCT.md → ARCHITECTURE / API / CONVENTIONS / DECISIONS / specs / AGENTS / CLAUDE"]
  D["**tstack-roadmap**<br/>full docs/ → ROADMAP.md"]
  P["**tstack-plan**<br/>milestone + docs → approved plan + branch"]
  E["**tstack-build**<br/>plan → implement → verify → merge → update status"]
  F["**tstack-specify**<br/>(iteration) add new feature → update docs + ROADMAP"]
  A --> B --> C --> D --> P --> E
  E -.next milestone.-> P
  F --> P

Loading

Four skills form a one-time setup chain (discover → product → architect → roadmap). Then tstack-plan and tstack-build form the per-milestone loop you run repeatedly. tstack-specify is the iteration skill for adding features after launch — it hands into the same plan → build loop.

The Seven Skills

Skill	When it triggers	Input	Output
tstack-discover	"I want to build…", new product idea, no brief yet	rough description	docs/1 - Discovery/business-brief.md
tstack-product	"let's write the PRD" after discovery	business brief	docs/PRODUCT.md
tstack-architect	"design the architecture" after PRODUCT.md	PRODUCT.md	ARCHITECTURE / API / CONVENTIONS / DECISIONS / specs + AGENTS.md + CLAUDE.md
tstack-roadmap	"make a roadmap" / "what do we build first"	full docs/ tree	docs/ROADMAP.md
tstack-plan	"plan milestone Mx" / "what should we build next"	ROADMAP.md + milestone-referenced docs	approved implementation plan + feature branch
tstack-build	"build it" / "ship this milestone" after a plan is approved	approved plan + feature branch	shipped milestone + merged branch + updated status
tstack-specify	"let's add feature X" in an established project	existing PRODUCT.md (+ ROADMAP.md)	updated docs + appended milestones

Install

This repo is the plugin. From a project where you want to use TStack:

# In Claude Code:
/plugin marketplace add tatejennings/tstack
/plugin install tstack@tstack

Once installed, the skills auto-trigger when their descriptions match what you say — no manual invocation required. You can also invoke explicitly with /tstack-discover, /tstack-plan, etc., if you want to skip the trigger phrase.

Quick Start

1. Start a new product idea — from a fresh project directory, say in Claude Code:

   "I want to build an app that helps freelancers track time across multiple clients."

   tstack-discover activates, interviews you, researches competitors, and writes docs/1 - Discovery/business-brief.md. Commit it and start a fresh session.

2. Walk the setup chain. In each new session, the next skill triggers from natural language:

   • "let's write the PRD" → tstack-product produces PRODUCT.md
   • "design the architecture" → tstack-architect produces the technical doc set
   • "make a roadmap" → tstack-roadmap produces ROADMAP.md

3. Per-milestone loop: for every milestone, run two skills back-to-back in the same session:

   • "plan milestone M0" → tstack-plan reads the milestone's referenced docs, branches, and produces an approved implementation plan
   • "build it" → tstack-build implements the plan, verifies "Done when" criteria, merges, and updates ROADMAP.md status

   Then loop into the next milestone (tstack-plan again). Repeat until the roadmap is done.

4. Add features after launch. When you want to extend the product, say:

   "I want to add a CSV import feature."

   tstack-specify activates, interviews you, proposes which docs need updates (with per-item approval), applies them, appends new milestones to ROADMAP.md, and hands off to tstack-plan for the first new milestone.

Output Structure (in a Consumer Project)

After running the setup chain, your project repo looks like:

your-project/
├── AGENTS.md                    # Single source of truth for AI agents
├── CLAUDE.md                    # → See @AGENTS.md
├── docs/
│   ├── PRODUCT.md
│   ├── ARCHITECTURE.md
│   ├── API.md
│   ├── CONVENTIONS.md
│   ├── DECISIONS.md
│   ├── ROADMAP.md
│   ├── 1 - Discovery/business-brief.md
│   └── 2 - Specs/
│       ├── database-schema.md
│       └── …

Right-Sizing

Not every project needs every artifact. tstack-architect will ask which level you want before writing anything:

Project complexity	Docs produced
Minimum (solo dev, single feature domain)	ARCHITECTURE.md · CONVENTIONS.md · TESTING.md · DECISIONS.md · AGENTS.md · CLAUDE.md
Standard (multi-feature app, API-driven)	+ API.md
Full (complex system, multiple services, team)	+ breakout specs in docs/2 - Specs/

DECISIONS.md and TESTING.md are mandatory at every size. tstack-architect records four foundational ADRs (security, observability, accessibility, privacy) before any other doc is written — regardless of project size. AI/LLM products get an additional ai-strategy.md spec.

Trigger Compatibility

TStack skills coexist with other Claude Code plugins, but a few descriptions overlap. Disambiguating phrases:

If you want…	Say	Avoids triggering
Plan the next TStack milestone	"plan milestone M3" / "plan the next milestone"	superpowers:writing-plans (which triggers on generic "write a plan")
Execute a TStack milestone	"build it" / "ship M3" / "implement the plan"	superpowers:executing-plans (generic plan execution)
TStack product discovery	"discover a new product" / "let's spec a new product idea"	superpowers:brainstorming (generic ideation)
TStack feature spec on existing project	"add a feature to this TStack project" / "spec a new feature"	tstack-product (which is for greenfield only)

In most cases auto-triggering picks the right skill because TStack descriptions include docs/PRODUCT.md / docs/ROADMAP.md prerequisites — superpowers skills don't reference those files, so Claude prefers the TStack skill when those docs exist. If you hit a collision in practice, invoke the skill explicitly: /tstack-plan, /tstack-build, etc.

Multi-Agent Support

TStack produces an AGENTS.md at your consumer repo's root as the single source of truth for all AI coding tools. Tool-specific config files just point to it:

Tool	Config file	Contents
Claude Code	CLAUDE.md	See @AGENTS.md
Cursor	.cursorrules	See @AGENTS.md
Codex	codex.md	See @AGENTS.md
Others	Their config	See @AGENTS.md

One place to update, every tool stays in sync.

Repo Layout

claude-code-starter/             # this repo = the plugin
├── .claude-plugin/plugin.json   # plugin manifest
├── skills/
│   ├── tstack-discover/         SKILL.md + references/full-guide.md
│   ├── tstack-product/          SKILL.md + references/full-guide.md
│   ├── tstack-architect/        SKILL.md + references/full-guide.md
│   ├── tstack-roadmap/          SKILL.md + references/full-guide.md
│   ├── tstack-plan/             SKILL.md (shares tstack-build's reference)
│   ├── tstack-build/            SKILL.md + references/full-guide.md
│   └── tstack-specify/          SKILL.md (no migrated reference — written from scratch)
├── README.md                    # you are here
├── CLAUDE.md                    # for someone editing the plugin
├── BACKLOG.md                   # plugin's own backlog of upcoming features
└── images/banner.jpg

Each skill's references/full-guide.md is the full original long-form prose — the SKILL.md is a concise procedural top-level, and the reference is consulted on demand.

License

MIT — use however you want.