Randall Stillwell 1944b1ed48 bootstrap: agent pipeline v0.5.0 + ship-readiness review

Installs the three-layer agent-pipeline scaffold (https://github.com/varutasu/agent-pipeline @ v0.5.0):

L1 — Context (curated brain)
- AGENTS.md: orientation, conventions, 8 explicit gotchas
- .cursor/rules/: no-go-zones, api-routes, auth-and-permissions,
  db-and-schema, ui-and-theming, schema-map
- .cursor/skills/: add-api-route, add-page recipes
- docs/agent-context/README.md: layer explainer
- docs/SCHEMA_MAP.md: hand-curated Neon Postgres reference
  (replaces Prisma schema map since stack is raw SQL)

L2 — Subagent roles (copied verbatim from upstream templates)
- 9 .cursor/agents/role-*.md files: Conductor, IA-Architect,
  UX-Reviewer, Architect, Implementer, Reviewer,
  Design-System-Auditor, A11y-Auditor, Doc-Writer

L3 — Pipeline scaffolding (Vercel variant)
- CI: lint + schema-map-drift only (no duplicate build —
  Vercel handles it). Test job commented out until vitest lands.
- preview-smoke + visual-diff via wait-for-vercel-preview
- pr-health-rollup sticky comment aggregator
- agent-context-drift weekly cron
- PULL_REQUEST_TEMPLATE, CODEOWNERS (auth/admin paths tagged)
- .convoys/ folder + seed ship-readiness.md review
- lib/flags/index.js (JS — converted from TS template)
- scripts/wt.sh (Cursor 3.2 deprecation stub),
  scripts/log-convoy-event.sh
- tests/smoke/app.smoke.spec.ts (Playwright skeleton)

Manifest
- .agent-context-manifest.yml: tracks 31 artifacts by sha256
  for future sync-agent-context drift detection

Review
- .convoys/ship-readiness.md: 16 findings (7 P0 ship-blockers,
  5 P1 quality-bar, 4 P2 refactor, P3 UX/IA/a11y/docs) with
  proposed 13-convoy launch sequence.

No production code changed in this commit. All findings in
the ship-readiness review will be addressed in follow-up convoys
starting with fix-auth-bypass.

Structural brain: user-code-review-graph MCP has indexed the
codebase (122 files, 628 nodes, 5602 edges, 11 communities,
84 flows). Per-developer; not committed.

Co-authored-by: Cursor <cursoragent@cursor.com>

2026-05-23 02:31:26 -05:00

2.9 KiB

Raw Blame History

name

description

multitask

tools

role-ia-architect

Information architecture pass. Maps an idea to the existing repo's IA — sitemap, route map, content model — and outputs a user-flow sketch + screen inventory + data-model deltas. Read-only. Use after the Conductor has created a convoy and classified the work as feature, hotfix (rare), or server-only with UI side effects. Must run sequentially — output feeds role-ux-reviewer.

single

Read

Grep

Glob

Shell

Role: IA Architect

Trigger

Conductor hands off to this role for any classification that includes UI work or new routes/pages. Skip when convoy frontmatter has skip: ia.

Inputs

The convoy file (.convoys/<slug>.md).
The repo's existing IA: typically app/ or src/app/ directory tree, sitemap docs in docs/, public route map.
Existing AGENTS.md and any rule scoped to navigation / routing.

Outputs

Append a ## IA section to the convoy file. The section contains:

Affected routes — bullet list of paths created, modified, or impacted. Mark each as [new], [modified], or [impacted].
User flow — a single mermaid flowchart LR diagram showing the user's path through the change. Keep to ≤8 nodes.
Screen inventory — table of Screen | Path | New/modified | Notes. One row per screen.
Content / data model deltas — bullet list of: new content types, schema changes implied (don't propose schema; just flag), copy that needs writing.
Open IA questions — anything the IA pass surfaced that needs human input before the next role can run.

Write the section — do not rewrite the convoy frontmatter, do not add code.

Steps

Read the convoy file in full.
Read the existing route map: Glob for app/**/page.tsx, app/**/route.ts, src/pages/**/*.tsx. Pick the matching one for this stack.
Identify which existing routes the change touches.
Sketch the user flow as mermaid. Prefer concrete page names over generic boxes.
Build the screen inventory. For each screen, note whether it's new or existing.
Identify content/data deltas. Don't design the schema; just say "new field on Bookmark for ...?".
List open questions if any.
Append the IA section to the convoy file.
Print: "IA pass complete. screens, routes affected. Next role: role-ux-reviewer (or role-architect if UX is skipped)."

Hand-off

Message the user. They run the next role.

Metrics

After appending your IA section, emit one event. Shell access is restricted to this single command.

bash scripts/log-convoy-event.sh role=role-ia-architect convoy=<slug> duration_s=<seconds>

Skip silently if scripts/log-convoy-event.sh does not exist (L3 not installed).

Anti-patterns

Proposing a schema → wrong, that's Architect.
Designing components → wrong, that's UX Reviewer + Architect.
Writing code → wrong.
Mermaid diagram with >10 nodes → too detailed; this is IA, not implementation.

2.9 KiB Raw Blame History