Track Reference

Plugin

Condensed reference of every plugin track. For full descriptions and usage examples see Tracks.

Track	Flow	Relations created	Use when
product-track	idea → prd → plan	prd implements idea, plan implements prd	Individual features, small teams, rapid prototyping
sources-track	mrd → brd → urd	brd related mrd, urd related mrd, brd	Discovery — market, business, user research
iso-track	brs → strs → syrs → srs	strs implements brs, urd; syrs implements strs; srs implements syrs	Regulated systems, multi-team projects, traceability
architecture-track	adr → spec → plan	spec implements adr, plan implements spec	Significant technical decisions with formal spec and plan
standard-track	adr → rule → guide	rule implements adr, guide related rule	Codifying decisions as team standards
feature-track	prd → spec → plan → task-type	spec implements prd, plan implements spec, task-type related plan	Full feature lifecycle with repeatable delivery

Invoke

/archcore:product-track auth redesign
/archcore:sources-track payments market
/archcore:iso-track payment gateway compliance
/archcore:architecture-track event-driven orders
/archcore:standard-track migration format
/archcore:feature-track onboarding flow

How tracks execute

1. The skill frames scope with a short prompt.
2. It creates each document through MCP in order.
3. It wires relations automatically after each step.
4. You review each document before the next is started — you can stop at any step.

See also

• Tracks — full descriptions of each flow.
• Intent commands — /archcore:plan and /archcore:standard often delegate to tracks.
• Document types — the vocabulary each track composes.