unfolding-architect
Architect role in the Unfolding Specs process. Decomposes Features into Tasks, creates System Tests, and identifies implicit technical assumptions as Architecture Decision Records (ADRs).
$ npx -y skills add t1/tdder --agent claude-codeShips with tdder. Installing the plugin gets this agent.
How it fires
How this agent gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
Context preview
The summary Claude sees to decide when to auto-load this agent.
Architect role in the Unfolding Specs process. Decomposes Features into Tasks, creates System Tests, and identifies implicit technical assumptions as Architecture Decision Records (ADRs).
A plugin for pi, Claude Code, and OpenCode that guides AI agents through disciplined Test-Driven Development and Clean Code practices. Note that currently this is WORK IN PROGRESS! I'm not even trying to keep it stable or tested.
Repo: t1/tdder
Other agents on tdder.
- clean-code-reviewer
Autonomous clean code review agent that analyzes code against clean code principles and returns prioritized refactoring suggestions. Spawned during TDD refactor phases or when explicitly requested for code review. <example> Context: TDD refactor phase completed user: "refactor
Open agent - unfolding-api-designer
API Designer role in the Unfolding Specs process. Acts as the API consumer's advocate — challenges the Feature spec from a consumer usability perspective, collaborates with the PO to refine assumptions, and designs API contracts (resource structure, endpoints, request/response
Open agent - unfolding-coder
Coder role in the Unfolding Specs process. Implements Tasks using TDD (Test-Driven Development), one test at a time, following the Red-Green-Refactor cycle.
Open agent - unfolding-po
PO (Product Owner) role in the Unfolding Specs process. Decomposes Features into smaller Features, creates Acceptance Tests, and identifies implicit business assumptions as Domain Model Decisions (DMDs).
Open agent - unfolding-ui-expert
UI Expert role in the Unfolding Specs process. Maps tech-agnostic UX components to concrete technology (CSS framework, interaction library, HTML structure). Commissioned by the Architect when a UX component has no mapping or the mapping is non-trivial.
Open agent - unfolding-ux-designer
UX Designer role in the Unfolding Specs process. Acts as the user's advocate — challenges the Feature spec from a usability perspective, collaborates with the PO to refine assumptions, and designs tech-agnostic user experience components (interaction flows, states, component
Open agent