Universal 8-phase methodology for planning and building enterprise-grade, mission-critical, and high-availability software systems. Compatible with leading AI coding agents.
Version: 2.0.0 | License: MIT | Language: π¬π§ EN / πͺπΈ ES
Author: Francisco J Bernades
GitHub: @exchanet
Repository: method_enterprise_builder_planning
- Banking & Fintech: Payment gateways, trading platforms, regulatory compliance systems
- Healthcare: HIPAA-compliant patient records, telemedicine platforms, medical device software
- E-commerce at scale: Multi-tenant SaaS, high-traffic marketplaces, distributed inventory systems
- Government & Defense: Security-first systems, audit trails, mission-critical infrastructure
- Enterprise SaaS: Multi-region deployments, 99.99% SLA requirements, GDPR/SOC2 compliance
- β Systematic architecture decisions documented as ADRs with rejected alternatives
- β Risk identification (STRIDE threat model) before writing code
- β Micro-task decomposition (β€50 lines) for parallel development
- β Test strategy with β₯99% coverage requirements
- β Compliance mapping (ISO 27001, GDPR, PCI-DSS, SOC2)
- β Automated quality gates via CI/CD templates
- β Evidence-based delivery with metrics and sign-off reports
- Method Modular Design β Core + Packs architecture pattern
- PDCA-T Method β Quality assurance cycle (β₯99% test coverage)
Method Enterprise Builder Planning is a universal hybrid framework combining:
- Structured prompt system for AI coding agents (Cursor AI, Claude Code, Kimi Code, Windsurf, Google Antigravity)
- Standalone executable tools (ADR Validator, Microtask Linter) for automated quality gates
- CI/CD integration templates for GitHub Actions, GitLab CI, Azure DevOps, and Jenkins
The name Builder reflects the method's comprehensive scope: it doesn't just plan β it orchestrates the complete construction of enterprise-grade software, from initial stakeholder analysis through architecture decisions, security hardening, micro-task decomposition, test strategy (β₯99% coverage), and evidence-based delivery sign-off.
Unlike agent-specific frameworks, this methodology works across 5 leading AI coding platforms:
| Agent Platform | Adapter | Installation |
|---|---|---|
| Cursor AI | .cursor/ rules + skills |
Express install or manual |
| Claude Code | CLAUDE.md + .claude/ |
Copy to project root |
| Kimi Code | KIMI.md |
Single file |
| Windsurf Cascade | WINDSURF.md |
Single file |
| Google Antigravity | AGENTS.md + GEMINI.md + .agent/skills/ |
Full skills package |
All adapters follow the same 8-phase protocol, ensuring consistency regardless of which AI agent you use.
Structured prompts guide the agent through systematic planning phases.
Executable tools provide deterministic validation that complements agent judgment:
- ADR Validator: 11 enterprise rules (structural, business, compliance) β blocks Accepted status if requirements not met
- Microtask Linter: Enforces β€50 effective lines per file, suggests automatic splits
- CI/CD Gates: Automated quality checks in your pipeline
What this guarantees: A systematic 8-phase planning process with automated quality enforcement at critical gates.
What it does not guarantee: Bit-perfect identical outputs on every run. The agent applies architectural judgment within the structure β which is the intended behavior for complex system design.
| Standard | Description |
|---|---|
| Enterprise-grade | Large-scale, high-user-load, complex transactions, strict security |
| Mission-critical | Failure has catastrophic financial or operational impact |
| High-availability | 99.999% uptime architecture (5 nines HA design) |
| Security by design | Security integrated from architecture, not bolted on after |
| Scalable system engineering | Handles massive data and transaction growth without performance loss |
| ACID Compliance | Atomicity, Consistency, Isolation, Durability for all transactions |
| RegTech / Compliance | ISO 27001, ISO/IEC 25000 (SQuaRE), CMMI level 3+, GDPR, SOC2, PCI-DSS |
| Component | What it does | Why it matters |
|---|---|---|
| Multi-Agent Support | Cursor AI, Claude Code, Kimi Code, Windsurf, Google Antigravity | Use with any leading AI coding agent β same methodology, same 8 phases |
| ADR Validator | CLI tool: 11 enterprise rules (structural, business, compliance) | Automated architecture quality gate β blocks Accepted status if requirements not met |
| Microtask Linter | Enforces β€50 effective lines per file | Enables parallel development β suggests automatic splits for oversized files |
| CI/CD Templates | Ready-to-use: GitHub Actions, GitLab CI, Azure DevOps, Jenkins | Quality gates in your pipeline: coverage check, microtask linting, delivery validation |
| Executable Tools | TypeScript validators with β₯99% test coverage | Deterministic validation β not just prompts, real automation |
Breaking change: Directory structure refactored for multi-agent support.
Old:.cursor/in root
New:agents/cursor/.cursor/,agents/claude-code/,agents/antigravity/, etc.
Automatic migration:
# Windows
powershell -File scripts/migrate-to-v2.ps1
# macOS / Linux
bash scripts/migrate-to-v2.shSee MIGRATION-v2.md for detailed migration guide.
Read the Banking Payment Authorization walkthrough β a real agent session building an enterprise payment system from scratch:
- Phase 1: Stakeholder map (product, security, compliance, DevOps)
- Phase 2: Micro-task backlog (32 tasks, β€50 lines each)
- Phase 3: Risk analysis (STRIDE threat model: SQL injection, MITM, privilege escalation)
- Phase 4-5: 7 ADRs with rejected alternatives (database choice, encryption, idempotency)
- Phase 6: TypeScript implementation with β₯99% test coverage
- Phase 7: Delivery report with metrics and compliance evidence
- Phase 8: Handover documentation for production deployment
No placeholders, no synthetic examples. Real outputs generated by the methodology.
| Domain | System Example | Key Requirements Addressed |
|---|---|---|
| Banking | Payment authorization gateway | PCI-DSS compliance, ACID transactions, fraud detection, audit trails |
| Healthcare | Electronic health records (EHR) | HIPAA compliance, data encryption, role-based access, consent management |
| E-commerce | Multi-tenant marketplace | Horizontal scaling, eventual consistency, idempotency, rate limiting |
| Insurance | Claims processing workflow | State machine design, SLA tracking, regulatory reporting, disaster recovery |
| Supply Chain | Real-time inventory tracking | High-availability architecture, distributed transactions, conflict resolution |
| Government | Citizen identity verification | Security by design, zero-trust architecture, GDPR compliance, penetration testing |
- Architecture: Microservices, event-driven, CQRS, saga patterns, API gateway
- Data: ACID transactions, eventual consistency, sharding, replication, data lakes
- Security: Zero-trust, encryption at rest/in-transit, RBAC, OAuth2/OIDC, audit logs
- Scalability: Horizontal scaling, caching strategies, CDN, load balancing
- Compliance: GDPR, HIPAA, PCI-DSS, SOC2, ISO 27001 mapping
For Cursor AI:
- Download repository as
.zipfrom GitHub β unzip - Copy folder path (e.g.,
C:\Users\your-name\Downloads\method-enterprise_builder_planning) - Cursor β New Agent chat β Paste path:
Install this method globally: C:\Users\your-name\Downloads\method-enterprise_builder_planning - Restart Cursor β Use with:
/method-enterprise_builder
For other agents:
# Clone repository
git clone https://github.com/exchanet/method_enterprise_builder_planning.git
cd method_enterprise_builder_planning
# Install for your agent
bash scripts/migrate-to-v2.sh --project=/path/to/your-project --agent=cursor
# Options: cursor, claude-code, kimi-code, windsurf, antigravityGlobal installation (available in all projects):
# Cursor AI
cp -r agents/cursor/.cursor ~/.cursor/
# Claude Code
cp agents/claude-code/CLAUDE.md ~/.config/claude/
cp -r agents/claude-code/.claude ~/.config/claude/
# Antigravity
cp agents/antigravity/AGENTS.md ~/.config/antigravity/
cp -r agents/antigravity/.agent ~/.config/antigravity/See agents/README.md for detailed installation per platform.
# Clone repository
git clone https://github.com/exchanet/method_enterprise_builder_planning.git
cd method_enterprise_builder_planning
# Copy agent-specific files to your project
# For Cursor AI:
cp -r agents/cursor/.cursor /path/to/your/project/
# For Claude Code:
cp agents/claude-code/CLAUDE.md /path/to/your/project/
cp -r agents/claude-code/.claude /path/to/your/project/
# For Antigravity:
cp agents/antigravity/AGENTS.md /path/to/your/project/
cp agents/antigravity/GEMINI.md /path/to/your/project/
cp -r agents/antigravity/.agent /path/to/your/project/Also install the companion methods:
# Method Modular Design (Core + Packs pattern)
git clone https://github.com/exchanet/method_modular_design.git
cp -r method_modular_design/agents/cursor/.cursor /path/to/your/project/
# PDCA-T Method (quality assurance cycle)
git clone https://github.com/exchanet/method_pdca-t_coding.git
cp -r method_pdca-t_coding/agents/cursor/.cursor/rules/METODO-PDCA-T.md /path/to/your/project/.cursor/rules/
cp -r method_pdca-t_coding/agents/cursor/.cursor/skills/metodo-pdca-t /path/to/your/project/.cursor/skills/Once installed, activate with any of these phrases:
/method-enterprise_builder
"Plan enterprise feature: [description]"
"Design mission-critical [system type]"
"Create ACID-compliant module for [feature]"
"Build high-availability [component] with 99.99% SLA"
"Implement security-first [module] with audit trail and GDPR compliance"
Cursor will guide you through the complete 8-phase cycle automatically.
PHASE 1: Enterprise Context Analysis
β System classification Β· Stakeholders Β· Regulatory environment
βΌ
PHASE 2: Non-Functional Requirements (NFR)
β Performance SLOs Β· Availability SLA Β· Scalability Β· Security Β· Compliance
βΌ
PHASE 3: Risk Matrix
β STRIDE threat model Β· Technical risk catalog Β· Mitigations
βΌ
PHASE 4: Micro-Task Decomposition (PDCA-T)
β Feature β Domain β Layer β β€50-line micro-tasks with dependency DAG
βΌ
PHASE 5: Architecture Decisions (ADR)
β Pattern selection Β· C4 diagrams Β· Pack mapping Β· ADR per decision
βΌ
PHASE 6: Security & Compliance Mapping
β STRIDE per module Β· RBAC matrix Β· ACID boundaries Β· Compliance matrix
βΌ
PHASE 7: Test Strategy
β Test pyramid Β· Coverage gates Β· Load tests Β· CI quality gates
βΌ
PHASE 8: Delivery Report
β Evidence-based sign-off Β· Test metrics Β· Security Β· Compliance checklist
method-enterprise_builder_planning/
βββ .cursor/
β βββ rules/
β β βββ METHOD-ENTERPRISE-BUILDER-PLANNING.md β main rule (trigger: manual)
β β βββ ENTERPRISE_ARCHITECTURE.md
β β βββ ENTERPRISE_SECURITY.md
β β βββ ENTERPRISE_SCALABILITY.md
β β βββ ENTERPRISE_COMPLIANCE.md
β β βββ ENTERPRISE_TESTING.md
β β βββ ENTERPRISE_MICROTASK_PLANNER.md
β βββ skills/
β βββ method-enterprise-builder-planning/
β βββ SKILL.md β main orchestrator skill
β βββ architecture-planning.md
β βββ security-planning.md
β βββ scalability-planning.md
β βββ compliance-planning.md
β βββ microtask-decomposition.md
β βββ testing-strategy.md
β βββ delivery-report.md
βββ core/
β βββ planning-engine/ β core layer (infrastructure only)
βββ packs/
β βββ enterprise-architecture-pack/
β βββ security-compliance-pack/
β βββ high-availability-pack/
β βββ testing-coverage-pack/
β βββ acid-compliance-pack/
βββ examples/
β βββ banking-walkthrough.md β β
complete executed walkthrough (start here)
β βββ banking-system-plan.md
β βββ high-availability-saas-plan.md
β βββ mission-critical-api-plan.md
βββ docs/
β βββ INSTALLATION.md
β βββ USAGE.md
β βββ ENTERPRISE-STANDARDS-REFERENCE.md
βββ README.md
βββ README.es.md
Validates Architecture Decision Records against 11 enterprise rules before marking them Accepted.
# Validate all ADRs in your project
node packs/enterprise-architecture-pack/validators/adr-validator/src/index.ts docs/adr/
# CI/CD (JUnit XML output)
node packs/enterprise-architecture-pack/validators/adr-validator/src/index.ts \
--format=junit --output=reports/adr-results.xml docs/adr/Validates that source files comply with the β€50 effective lines rule, with split suggestions.
# Validate a single file
node packs/enterprise-microtask-planner-pack/validators/microtask-linter/src/index.ts \
--task=src/payments/domain/money.ts
# Validate all files in a directory
node packs/enterprise-microtask-planner-pack/validators/microtask-linter/src/index.ts \
--dir=src/ --recursive# Copy GitHub Actions workflow to your project
cp .ci-cd/templates/github-actions/workflow-enterprise-builder.yml \
.github/workflows/enterprise-builder.ymlAvailable for: GitHub Actions, GitLab CI, Azure DevOps, Jenkins. See .ci-cd/README.md.
Each pack and the Core include a config.schema.json that documents configurable parameters.
Some fields carry x-ui annotations (e.g. "widget": "slider", "widget": "checkbox-group").
These are design markers for a future configuration UI β no GUI currently renders them. They serve two purposes today: documenting the intended UX for each field, and helping the Cursor AI agent describe options in natural language. They have no runtime effect.
| Pack | Activated in phase | Provides |
|---|---|---|
enterprise-architecture-pack |
Phase 5 | ADR templates, C4 diagrams, pattern decision trees |
security-compliance-pack |
Phase 3, 6 | STRIDE templates, RBAC matrices, audit checklists |
high-availability-pack |
Phase 2, 5 | SLA/SLO definitions, failover strategies, chaos engineering |
testing-coverage-pack |
Phase 4, 7 | Test pyramid, coverage requirements, load test templates |
acid-compliance-pack |
Phase 4, 6 | Transaction boundaries, rollback strategies, idempotency |
| Method | Role |
|---|---|
| Method Modular Design | Architecture pattern (Core + Packs) used for all generated code |
| PDCA-T Method | Quality cycle (β₯99% coverage) applied to every micro-task |
MIT β see LICENSE file.
Francisco J Bernades
GitHub: @exchanet