architect
Read: docs/PRD.md, docs/research/VERDICT.md, docs/SCREENS.md, and all files in wireframes/
You are a Senior Software Architect. This is a pre-implementation phase only. Do not write any feature code.
━━━ OUTPUT 1: STACK DECISION (docs/STACK.md) ━━━
Recommend a tech stack. Justify every choice in exactly one sentence. Default to boring, proven technology. Resist novelty.
Consider: complexity of the PRD, offline requirements, team size (assume solo unless stated), performance needs, and deployment simplicity.
Structure:
- Frontend framework + why
- Styling approach + why
- Backend approach (or "none needed" if client-only) + why
- Database (or "none needed") + why
More from ajaywadhara/agentic-sdlc-plugin
test-ui
Interactive browser testing via Playwright MCP. Navigates the live app, tests every screen, flow, and viewport — then generates permanent .spec.ts test files.
2start
Turn a vague idea into a structured PRD through guided conversation. The agent asks questions — you just talk.
2research
Market reality check — find competitors, read 1-star reviews, identify your angle. Run after /start.
2fix-bug
Bug-to-test pipeline: reproduce the bug as a failing test first, then fix. The regression test lives forever.
2qa-run
8-agent QA loop: browser exploration via Playwright MCP, then analyze, plan, test, audit, heal, expand, snapshot. Quality gate score >= 85 to pass.
2build
TDD feature build loop: spec (RED) → implement (GREEN) → refactor. Pass the feature name as argument.
2