⚠️ Sample Project — Not Production-ReadyThis project is provided as a sample and reference implementation only. It is not designed, tested, or hardened for production use. Use it as a starting point or learning resource, and perform your own security review, testing, and operational hardening before deploying to any production environment. See SECURITY.md for known gaps and production hardening guidance.
Compress the idea-to-production loop with disciplined AI adoption.
Part of the PRISM Framework (Progressive Readiness Index for Scalable Maturity) — the D1 Velocity pillar focuses on AI-native software development lifecycle practices that are measurable from Day 1.
PRISM D1 instruments how your teams actually use AI to write software — which commits AI wrote, whether that code passes review and survives in production, and what it costs — then renders it on dashboards aimed at engineers, engineering leaders, and CISOs.
The Executive Readout, running on real data. The observed PRISM level is computed from live outcome metrics rather than self-assessed, with a gate table naming what blocks the next level. AI share, merge rate and cost per shipped commit come from commit attribution — and Attribution Coverage reports what fraction of the fleet those numbers actually cover, so a partially-onboarded team is never mistaken for a partially-AI one.
Install prism-cli (Node.js 22 or later): npm install -g @prism-d1/cli. Most features run on a developer machine with no AWS deployment.
| Feature | Command | Details |
|---|---|---|
| Secret scan on commit, AI review on push | prism-cli enable codewatch |
Codewatch |
| One local page for results, usage and setup | prism-cli dashboard |
Local Dashboard |
| Findings, spend and setup status for an AI agent (Kiro, Claude Code) | prism-cli mcp |
MCP server |
| Findings in VS Code, Kiro or Cursor | code --install-extension prism-d1-<version>.vsix |
Editor extension |
| A PRISM page, PRISM tools, a fix-findings skill and a quiet daily digest in Kiro Crew | prism-cli enable kirocrew |
Kiro Crew app |
| PRISM tools, slash commands, a findings summary at session start, and a secret and review check before Claude pushes in Claude Code | /plugin install prism@prism-d1-velocity |
Claude Code plugin |
| Findings and spend in the Claude Code status line | prism-cli enable claude-code |
Claude Code status line |
| Read-only AWS account checks and fixes | prism-cli aws check |
AWS Account Advice |
Security Agent review of your branch (after enable security, which deploys to AWS) |
prism-cli security code-review |
Running a Review |
PRISM brings codewatch findings, review reports, AI spend and the setup checklist into the tools you already code in:
| Plugin | Works with | What you get | Install |
|---|---|---|---|
| PRISM editor extension | VS Code, Kiro IDE, Cursor | Findings in the Problems panel, spend and findings in the status bar, a PRISM panel with reports and setup. Works with or without a repo open, and over Remote-SSH. | Install the editor extension |
| PRISM Kiro Crew app | Kiro Crew | A PRISM sidebar page, PRISM tools for every agent, a skill that fixes findings before a push, and a daily digest that notifies you only when something changed. | Install the Kiro Crew app (prism-cli enable kirocrew) |
| PRISM Claude Code plugin (v0.3.1) | Claude Code | The PRISM MCP tools, slash commands (/prism, /prism:findings, /prism:report, /prism:fix, /prism:review, /prism:spend, /prism:dashboard for the local dashboard on 127.0.0.1, or --snapshot for a static file), a SessionStart summary of the branch's open findings, the agent harness loop hooks (gitleaks and a review before Claude pushes, and an opt-in review before it finishes), and a status line with findings and spend (prism-cli enable claude-code). |
Install the Claude Code plugin (/plugin marketplace add aws-samples/sample-prism-d1-velocity, then /plugin install prism@prism-d1-velocity) |
Any other MCP client, including Kiro, can use the same tools through prism-cli mcp. Feature-by-feature comparison and details: Using PRISM locally. Every command and flag: command reference. What each command touches in AWS: prism-cli Overview.
⚠️ Node.js 22 is required. codeburn needs Node.js 22+ for AI usage telemetry. Install via nodejs.org or nvm:nvm install 22 && nvm use 22.
Also requires AWS CLI v2 and CDK v2 (npm install -g aws-cdk).
node --version # must be v22.x or later
npm install -g @prism-d1/cli codeburn
git clone https://github.com/aws-samples/sample-prism-d1-velocity.git
cd sample-prism-d1-velocity/infra
npm install
npx cdk bootstrap # first time in this account/region only
npx cdk deploy --all -c skipVpc=true # skipVpc saves ~$35-50/mo; drop it for prodThis creates the EventBridge bus, Lambda processors, DynamoDB tables (KMS-encrypted), 4 CloudWatch dashboards, alarms, Bedrock Guardrails, and the OTEL collector. Note the OtelCollectorUrl and OtelUserPoolId stack outputs — you need both below.
# username MUST be the developer's email
aws cognito-idp admin-create-user \
--user-pool-id <OtelUserPoolId> \
--username dev@example.comOr with prism-cli: prism-cli team info (read-only) prints both outputs and the line to send developers, and prism-cli team add-developer dev@example.com creates the account after showing the plan and asking (--dry-run to preview).
npm install -g @prism-d1/cli
prism-cli enable codeburn --url <OtelCollectorUrl>--url puts codeburn in team mode. It installs codeburn if it is missing (it asks first), signs you in, backfills 30 days and installs a schedule that pushes usage and git commit attribution every 12 hours. Preview it with --dry-run and check it with --status; the other modes and flags are in Developer Setup.
Open the PRISM-D1-Team-Velocity dashboard in CloudWatch. Within one sync cycle you should see AI-vs-human commit counts and an Attribution Coverage percentage.
Coverage is the number to watch first. It compares commits your CI observed (a complete census) against commits attribution actually captured (a sample of onboarded machines). Below 80%, every AI metric is understating reality — the fix is getting more developers through step 3, not changing the dashboard.
Wire up CI so delivery metrics and eval gates start reporting:
prism-cli bootstrapper setup-github-oidc --global # or setup-gitlab-oidc
prism-cli bootstrapper install-github-workflows --region us-west-2Full instructions for OIDC, per-repo workflows, eval gates, the AWS Continuum security agent, VPC options, and cost tuning are in the User Guide.
| Guide | For | Contents |
|---|---|---|
| User Guide | Engineers deploying and using PRISM | Setup, local tools (codewatch, dashboard, editor extension, MCP, Kiro Crew app), security scans, AWS checks, CI/CD workflows, eval gates, dashboards, agent development, troubleshooting |
| Data Architecture | Anyone extending it | Data sources, event schema, the attribution pipeline, metrics catalog with known gaps, alarms, dashboard design decisions |
| Bedrock Protection | Engineers and security leaders | Layered defence against LLMjacking: gitleaks in CI and full-history repo scans, IAM credential hygiene, Bedrock spend guardrails across both billing surfaces |
| Leader Guide | Engineering leaders | Executive readout template, ROI model, maturity progression |
| Why Local Code Review | Engineering leaders | The evidence for reviewing changes before push, why the reviewer should be a separate model or agent, how PRISM does it, its limits and what to measure |
| prism-cli Overview | Engineering managers | The prism-cli commands by job, what each costs and touches in AWS, safety defaults, decisions and open questions |
| prism-cli Command Reference | Anyone running prism-cli | Every command and flag, generated from --help |
| Editor extension, Kiro Crew app, Coding agent | Users and maintainers of each component | Install, features, security, build and release |
| Assessment Guide | Solutions Architects | Scanner categories, interview questions and rubrics, scoring, qualification matrix |
| Customer Onboarding | Solutions Architects | Onboarding tracks, email templates, per-track pre-work |
| Roadmap | Contributors | Prioritized backlog |
Four CloudWatch dashboards, all reading the events table and attribution store directly so full history is available and empty panels name the emitter that is missing.
- Team Velocity — delivery KPIs, AI-DORA KPIs, contribution and quality trends, per-repo breakdown, eval gates, governance, agents, and security with remediation SLA. Delivery figures are labeled as proxies (merge frequency, PR cycle time, revert rate) until real deploy and incident integrations exist.
- Executive Readout — business outcomes and an observed PRISM level computed live from outcome metrics, with a gate table showing what blocks the next level. Plus unit economics, AI-vs-human quality, and a condensed security strip.
- CISO Compliance — exposure and finding aging, per-severity remediation SLA with breaches named, AI code risk normalized per 100 commits, shift-left effectiveness with a computed finding survival rate, CWE and compliance-framework coverage, runtime governance.
- Developer Productivity — org and per-developer AI output and spend, fed entirely by codeburn attribution with no CI instrumentation or git hooks.
- ~5-hour workshop (4h40m of modules 01–06, plus 30min prerequisites and optional extensions) using Claude Code, Kiro, and Bedrock
- Spec-driven development templates with AI-DLC steering files (adapted from awslabs/aidlc-workflows)
- AI agent development — Strands SDK, MCP with scope-based auth, Amazon Bedrock AgentCore
- Bootstrapper code — CI workflows, eval harnesses, agent configs, spec templates teams inherit on day one
- Bedrock Guardrails — content filters, PII protection, denied topics with per-trigger metrics
- MCP Authorization — scope-based tool access control with audit trail
- Eval Gates — agentic code review via kiro-cli headless, gitleaks secret scanning, and an AWS Continuum finding gate
- KMS encryption on all data stores, VPC isolation, exfiltration detection
An autonomous coding agent that takes a GitHub issue, reproduces the bug, fixes the code, writes a regression test, verifies with the project's own test suite, and opens a PR — all inside an Amazon Bedrock AgentCore harness.
Issue labeled `agent-fix` → GitHub Actions → AgentCore harness (microVM) → PR with summary
- Strands SDK agent with file_read, file_write, shell, git_ops tools
- Claude Sonnet 5 default model (~$0.30-0.50 per issue fix)
- REPRODUCE → FIX → TEST → VERIFY workflow enforced by system prompt
- Full OTEL telemetry — tokens, cost, commit attribution flow through the same pipeline as human AI-assisted work
- Rich PR/issue comments — model-generated summary, token count, cost, run link
- One image, any toolchain — mise installs from
.tool-versionsat session start
Deploy once per account, install per-repo with prism-cli bootstrapper install-coding-agent. Full documentation: Coding Agent README.
The four classic DORA metrics plus three AI-specific dimensions. Source is what actually computes each metric today, and Status flags where the pipeline is incomplete — the DORA metrics are currently proxies.
| Metric | Source | Status | L2 Target | L4 Target |
|---|---|---|---|---|
| Deployment Frequency | Merged PRs/day (prism-ai-metrics.yml on PR merge) |
Weekly | Daily+ | |
| Lead Time for Changes | PR created → merged, p50 | < 1 week | < 1 day | |
| Change Failure Rate | % of merged PRs titled revert|hotfix|rollback |
< 15% | < 5% | |
| MTTR | Revert/hotfix PR open → merge | < 24h | < 1h | |
| AI-to-Merge Ratio | codeburn attribution spans | ✅ Works, hook-free | >= 20% | >= 45% |
| Post-Merge Defect Rate | Reverted / merged AI commits (attribution) | ✅ Works, hook-free | <= 1.2x human | <= 0.9x |
| Eval Gate Pass Rate | kiro-cli headless review in CI | ✅ Works | >= 80% | >= 95% |
All four delivery proxies aggregate over the dashboard's selected time range. The ✅ rows come from codeburn attribution rather than git commit trailers, so they survive the commit-trailer hook's retirement.
| Level | Name | What It Looks Like |
|---|---|---|
| L1 | Experimental | Ad hoc AI use, no metrics, no shared tooling |
| L2 | Structured | Claude Code + Kiro adopted, acceptance tracked in CI |
| L3 | Integrated | Eval gates in pipeline, AI-DORA dashboards live, spec-driven workflow |
| L4 | Orchestrated | Multi-team platform, AI FinOps, governed agent scope, security agent |
| L5 | Autonomous | Agents contributing to architecture, >20% autonomous deployments |
The Executive Readout computes an observed level from live outcome metrics, capped at L4 — L5 requires an autonomy signal no emitter produces. That is deliberately distinct from the assessment scanner's capability score, and divergence between the two is informative: capability without outcomes means tooling is installed but unused.
Hosted on AWS Workshop Studio: PRISM D1: Velocity Workshop
| # | Module | Duration | Key Outcome |
|---|---|---|---|
| 00 | Prerequisites | 30 min | Environment ready, Bedrock access confirmed |
| 01 | AI-SDLC Foundations | 45 min | Claude Code configured, first AI-assisted commit |
| 02 | Agent Development | 70 min | Strands agent + MCP server with auth + multi-agent orchestration |
| 03 | Spec-Driven Development | 45 min | Spec-driven development with Kiro or Claude Code |
| 04 | Instrumenting AI Metrics | 45 min | CI emitting events to EventBridge |
| 05 | Eval Gates in CI/CD | 45 min | Agentic kiro-cli code review + security finding gate blocking bad merges |
| 06 | Dashboards & Visibility | 30 min | 4 CloudWatch dashboards live |
Extensions: security design review (+10 min, Module 03), code review (+10 min, Module 05), CISO dashboard walkthrough (+5 min, Module 06).
prism-cli assessment web # opens http://localhost:3120Scan a repository, run the 20-question interview (manually or with an AI agent via Bedrock), and generate an HTML report. See the Assessment Guide for methodology and Customer Onboarding for what happens next.
This project is licensed under the MIT License.

