A2P: An MCP Server That Enforces Engineering Discipline for AI Coding Agents

What A2P Does

A2P (Architect-to-Product) is an AI engineering framework packaged as an MCP server designed to address common problems with AI coding agents like Claude Code. Instead of just providing more tools, A2P enforces engineering discipline through a gated workflow system.

Core Workflow

The framework implements a lifecycle with enforced gates: Architecture → Plan → Build → Audit → Security → Deploy. Each feature slice must progress through: RED → GREEN → REFACTOR → SAST → DONE.

This enforcement is implemented in code. If an agent tries to advance without satisfying a gate requirement, the tool throws an error.

Specific Enforcement Examples

• A slice cannot advance unless test evidence exists
• Security scanning runs as part of the workflow, not at the end
• Deploy can be blocked until SSL/HTTPS is verified
• Secret management must be defined before deploy configs are generated
• Stateful systems cannot pass deploy without backup requirements
• Release decisions and signoff points are explicit, not hand-waved in prompts

Additional Features

The creator integrated codebase-memory-mcp for structural code exploration, allowing the agent to understand repositories more efficiently instead of "grep-walking everything."

Use Cases

The framework is designed for two primary scenarios:

1. Starting a new project with guardrails: Define architecture → break it into slices → build with gated TDD → security → deployment artifacts
2. Hardening a vibe-coded MVP: Skip straight to security, audit, refactor, and deployment readiness

Technical Details

A2P is open source under the MIT license. The repository is available at github.com/BernhardJackiewicz/architect-to-product.

The creator specifically seeks critical feedback from developers already using Claude Code seriously, asking about the biggest failure modes in current AI coding workflows: tests, security, architecture drift, fake "done," or deployment issues.