多智能体框架

Prerequisites

• Kiro CLI installed
• Python 3.9+ (for hooks)
• Node.js 18+ (for UI/UX Pro Max skill — optional)

Requirements gate every spec

The PM runs first, always. No agent creates spec.md or tasks.md until the user has confirmed the PRD. This prevents the most common failure mode in AI-assisted development: building the wrong thing confidently and completely.

Getting Started

Setup

```bash

Solution options before commitment

After gathering requirements, the PM proposes two meaningfully different approaches — not just "simple vs complex", but trade-offs that reflect the user's real constraints (team size, timeline, budget, expected scale). The user chooses the direction before any architecture work begins.

UI/UX — Interface Designer

Triggered by Architect immediately after planning, before any implementation.

• Optionally installs the UI/UX Pro Max skill (67 UI styles, 161 palettes) via npx uipro-cli init --ai kiro
• Produces HTML mockups for every screen defined in the spec
• Output: ui/screens/NN-name.html per screen, ui/transitions/flow.html (animated flow), ui/index.html (navigation hub), ui/design-system.md

Model: claude-sonnet-4.6 | MCPs: context7

---

Open Kiro CLI in your project directory

cd /path/to/your-project kiro ```

The pm agent is the default agent and starts automatically.

Agent Pipeline

┌─────────────────────────────────────────────────────────────────────┐
│                          USER REQUEST                               │
└───────────────────────────────┬─────────────────────────────────────┘
                                │
                                ▼
              ┌─────────────────────────────────┐
              │          PM AGENT               │
              │                                 │
              │  Turn 1: Discovery questions    │◄── User answers
              │  Turn 2: 2 solution options     │◄── User chooses
              │  Turn 3: PRD + summary          │◄── User confirms
              │  Turn 4: Dispatch               │
              └─────────────────┬───────────────┘
                                │ confirmed PRD
                                ▼
              ┌─────────────────────────────────┐
              │        ARCHITECT AGENT          │
              │                                 │
              │  Reads PRD → writes spec.md     │
              │  Writes tasks.md (groups)       │
              │  Runs execution loop            │
              └──┬──────────────────────────────┘
                 │
       ┌─────────┼─────────────────────────────────┐
       │         │                                 │
       ▼         ▼                                 ▼
  ┌─────────┐ ┌─────────┐                   ┌───────────┐
  │  UI/UX  │ │  CODER  │ ··· (per group)   │    OPS    │
  │ mockups │ │  impl.  │                   │  infra    │
  └─────────┘ └─────────┘                   └───────────┘
                 │ all groups complete
                 ▼
       ┌──────────────────┐     ┌──────────────────┐
       │    REVIEWER      │────►│ SECURITY REVIEWER │
       │  code quality    │     │  OWASP / secrets  │
       └──────────────────┘     └──────────────────┘
                                        │ PASS
                                        ▼
                              ┌──────────────────┐
                              │   DOCS AGENT     │
                              │ arc42 + C4 + README│
                              └──────────────────┘

---

Workflows

PM Discovery Questions

The PM asks across eight categories, phrased for business stakeholders — not developers:

Sample questions in business language: - "What's the cost of NOT having this? Time lost, mistakes made, revenue not captured?" - "How do people cope today — spreadsheet, manual process, another tool, or nothing?" - "How fast does it need to feel? Is a 2-second load acceptable, or does it need to be instant?" - "Who signs off before this ships?"

---