| name | amaa-prrd-trdd-kanban |
| description | ARCHITECT's role in the PRRD / TRDD / Kanban workflow. Use when ARCH shapes a proto-TRDD into a full TRDD, decides whether to split (1→N), group (N→1), or pass-through, authors all the verification / impact / delivery frontmatter, and writes the prose body with acceptance criteria. |
| allowed-tools | Bash(python3:*), Bash(get-prrd.py:*), Bash(findprrd.py:*), Bash(findtrdd.py:*), Bash(kanban.py:*), Read, Edit, Grep, Glob |
| metadata | {"author":"Emasoft","version":"1.0.0"} |
Overview
The ARCHITECT (AMAA) layer of the PRRD / TRDD / Kanban model. ARCH
owns the design column — the only column with a 1→N (split) and
N→1 (group) topology. A proto-TRDD comes in from ORCH; one or more
fully-designed TRDDs land in dispatch. For universal mechanics, see
the prrd-trdd-kanban skill in ai-maestro-plugin.
ARCH is exempt (no MANAGER approval) for all within-team design
work: pass-through, split, group, setting design frontmatter.
Non-exempt (request approval): force-superseded outside a normal
split, editing TRDDs already past design.
Prerequisites
- The universal
prrd-trdd-kanban skill in ai-maestro-plugin is
available (mechanics, transition numbers, exempt-operations list).
- The project PRRD exists and
design/tasks/ is present.
- A proto-TRDD sits in the
design column awaiting ARCH.
Instructions
- Read the proto-TRDD body (the paraphrased user request).
- Set
task-type: (feature / bugfix / refactor / docs /
infra / security / artifact / spike / audit).
- Set
severity: and effort: from judgment.
- Set
release-via: (publish for tools/packages, deploy for
services, none for internal-only).
- Set
test-requirements:, audit-requirements:,
review-requirements: (which test/scan/review types are mandatory).
- If artifact-producing, set
artifact-kinds:; set runtime-targets:
(platforms that must pass) and impacts: (install / dependencies /
config / migration / public-api / ci-pipeline).
- Identify NPT children — prerequisites that must complete BEFORE
the parent's
dev. Author each as a separate TRDD; link via npt:.
- Identify EHT children — consequence-handling tasks that must
complete BEFORE the parent's
complete. Link via eht:.
- Decide topology: pass-through (#4
design → dispatch), 1→N
split (#5 parent → superseded, N children to dispatch), or
N→1 group (one combined TRDD supersedes the inputs).
- Write the body:
## STATE (if multi-session), ## Acceptance criteria (testable bullets), ## Design notes, ## Out of scope;
cite rules in relevant-rules:.
- Move on: pass-through sets
column: dispatch, assignee: null,
bumps updated:. On split/group, mark the parent/inputs
column: superseded with superseded-by: [<child-refs>].
Output
- A fully-designed TRDD: complete frontmatter (task-type, severity,
effort, release-via, the three requirement sets, runtime-targets,
impacts, npt/eht, relevant-rules) plus the prose body.
- On a split/group: N child TRDDs (fresh UUID + timestamp,
parent-trdd:/supersedes:, own requirements) and the superseded
parent/inputs.
- An AMP message to ORCH via COS: "TRDD- designed; ready for
dispatch" (or "split into : " / "grouped into ").
- New/edited TRDD files staged and committed.
Error Handling
- Ambiguous scope — do not guess. Ask ORCH for clarification via
COS before designing.
- Too big for one TRDD — split it 1→N rather than shipping an
oversized proto-TRDD downstream.
- Recurring design constraint — when a pattern recurs across N
TRDDs, or a library/boundary choice should be project-wide, file a
PRRD proposal (
prrd-edit.py propose silver ... --routed-via cos-<team>) instead of re-deciding per TRDD.
- Edit past design / force-supersede outside a split — non-exempt;
request MANAGER approval first.
Examples
1→N split. Proto-TRDD "add OAuth + audit logging" holds two
independent jobs. ARCH authors two children (each with fresh UUID,
supersedes: [<parent>], own test/audit requirements), sets the
parent column: superseded, superseded-by: [<both>], commits, and
AMPs ORCH via COS: "TRDD-7a1 split into 2: , ".
Setting requirements (pass-through). Proto-TRDD "fix login race"
→ task-type: bugfix, severity: high, release-via: deploy,
test-requirements: [unit, integration], review-requirements: [code-review]. ARCH writes acceptance criteria, sets
column: dispatch, assignee: null, commits.
Resources
For the full Kanban mechanics, transition numbers, and the exempt /
non-exempt boundary, consult the universal prrd-trdd-kanban skill in
ai-maestro-plugin, and within it the trdd-frontmatter-schema.md
reference (every field ARCH sets) and the exempt-operations.md
reference (transitions that skip MANAGER approval).
