Arckit Oaa Adm Lite

You are helping an enterprise architect create an O-AA ADM Lite architecture using Open Agile Architecture (O-AA, C208) mapped to TOGAF ADM phases across agile sprints. This approach compresses the full ADM cycle into a sprint-driven engagement suitable for rapid delivery windows.

User Input

$ARGUMENTS

Trigger Guidance

Use this command when any of the following conditions are met:

• Client engagement has a hard timeline under 8 weeks for architecture + initial delivery

• Client operates in agile/sprint-driven development culture

• First engagement with a client — rapid architecture vision needed before scoping sprints

• Client requires TOGAF alignment but cannot sustain traditional ADM cadence (quarterly architecture boards, 200-page deliverables)

Do NOT use when:

• Full regulatory audit trail is required (use $arckit-adm-preliminary with full ADM workflow instead)

• Multi-year enterprise transformation with 50+ stakeholder review gates

• Architecture baseline phase requires extensive current-state assessment (> 4 weeks)

Prerequisites: Read Foundational Artifacts

Note: Before generating, scan projects/ for existing project directories. For each project, list all ARC-*.md artifacts, check external/ for reference documents, and check 000-global/ for cross-project policies. If no external docs exist but they would improve output, ask the user.

RECOMMENDED (read if available, note if missing):

• PRIN (Architecture Principles, in 000-global) — Extract: Guiding principles, decision framework, technology standards

  • If missing: warn user to run $arckit-principles first. Even O-AA Lite benefits from established principles.

• ADMP (ADM Preliminary / Architecture Vision) — Extract: Existing scope, drivers, constraints if a preliminary ADM was already done

  • If missing: note that Sprint 0 will establish vision from scratch

Prerequisites 1b: Read external documents and policies

• Read any external documents listed in the project context (external/ files) — extract existing vision documents, strategic plans, enterprise architecture mandates

• Read any enterprise standards in projects/000-global/external/ — extract architecture vision statements, enterprise transformation plans, cross-project alignment documents

Instructions

1. Identify or Create Project

Identify the target project from the hook context. If the user specifies a project that doesn't exist yet, create a new project:

1. Use Glob to list projects/*/ directories and find the highest NNN-* number (or start at 001 if none exist)
2. Calculate the next number (zero-padded to 3 digits, e.g., 002)
3. Slugify the project name (lowercase, replace non-alphanumeric with hyphens, trim)
4. Use the Write tool to create projects/{NNN}-{slug}/README.md with the project name, ID, and date
5. Also create projects/{NNN}-{slug}/external/README.md with a note to place external reference documents here
6. Set PROJECT_ID = the 3-digit number, PROJECT_PATH = the new directory path

2. Read Template

Read the template (with user override support):

• First, check if .arckit/templates-custom/oaa-adm-lite-template.md exists in the project root

• If found: Read the user's customized template (user override takes precedence)

• If not found: Read .arckit/templates/oaa-adm-lite-template.md (default)

• Then, read .arckit/templates/_partials/RENDERING.md and resolve the template's <!-- DOC-CONTROL-HEADER --> marker to the Document Control partial it selects, applying the ${organisation_name} and ${default_classification} substitutions. Remove the marker and its comment from the output — a rendered artefact must never contain either.

• Also apply the O-AA placeholder substitutions in .arckit/references/placeholder-substitutions.md (${project_issue_prefix}, ${safety_checklist_id}, ${references_dir}) wherever they appear in the template.

Tip: Users can customise templates with $arckit-customize oaa-adm-lite

3. Sprint Map

The O-AA ADM Lite maps the TOGAF ADM cycle to agile sprints:

4. O-AA Axiom Alignment

Every O-AA deliverable must reference the relevant published O-AA axioms (C208, Scope and axioms). The axioms this sprint-mapped engagement applies:

• Axiom 1 (Customer Experience Focus) — Sprint 0 vision is anchored on customer outcomes, not on artefacts

• Axiom 3 (Rapid Feedback Loops) — short sprint cycles with per-sprint architecture review are the O-AA feedback cadence

• Axiom 5 (Value Stream Alignment) — each sprint maps to the ADM phase that advances value along the stream

• Axiom 6 (Autonomous Cross-Functional Teams) — the sprint team owns architecture decisions end-to-end, without a central architecture board

• Axiom 7 (Authority, Responsibility, and Accountability Distribution) — the operational model (who monitors, who responds, who is accountable) is defined alongside the technical stack, and governance distributes decision authority instead of centralising it

• Axiom 10 (Simple Common Operating Principles) — shared artefacts and one quality checklist keep every sprint consistent

• Axiom 14 (Bias for Change) — the implementation plan enables rapid delivery with governance built in

• Axiom 15 (Project to Product Shift) — the organising principle of the engagement is the product, not a one-off project

Cite axioms by published number and name. Do not quote axiom text you cannot verify against C208 — if a claim cannot be traced to the standard, drop the attribution.

5. Sprint Artefact Definitions

O-AA ADM Lite defines YAML sprint artefacts whose structure is inlined in oaa-adm-lite-template.md. These artefacts are deliverables owned by this command, not shared schema files:

• vision.yaml — Architecture vision, scope, drivers, constraints (Sprint 0; consistent with the scope and vision established by $arckit-adm-preliminary)

• implementation-strategy.yaml — Implementation waves, migration strategy (Sprint 3; consistent with $arckit-transition-architecture)

• stakeholder-map.md — Stakeholder roles, concerns, compliance mapping

Validate each artefact against the inlined structure in the template before writing it, and run $arckit-health after the build to catch stale or orphaned artefacts.

6. Generate O-AA ADM Lite Document

Create the O-AA ADM Lite document following the template structure.

Document Control

• Generate Document ID with node scripts/generate-document-id.mjs {P} OAAL --filename (canonical form: ARC-{P}-OAAL-v1.0)

• Set owner, dates, status, classification

• Review cycle: Per sprint cycle

Sprint Plan

• Define sprint duration (default: 2 weeks)

• Map each sprint to TOGAF ADM phases

• Specify deliverables per sprint with acceptance checks

• Include sprint-level acceptance criteria

Sprint 0: Vision + Stakeholders

• Use vision.yaml schema

• Map stakeholders to concerns and compliance requirements

• Define success criteria with measurable targets

• Architecture contract: deliverable format and handoff process

Sprint 1-2: Architecture Design

• Business + Data Architecture (Sprint 1)

• Technology Architecture (Sprint 2)

• Each sprint produces YAML artefacts whose structure is defined in the template

Sprint 3: Implementation Wave

• Use implementation-strategy.yaml schema

• Define migration approach, work packages, sequencing

• Risk assessment per work package

Sprint 4+: Governance + Change

• Lightweight governance cadence (sprint reviews, not quarterly boards)

• Continuous compliance evidence

• Architecture change requests via $arckit-architecture-change

7. External References

Populate the ## External References section per .arckit/references/citation-instructions.md. Every claim taken from an external/ document, a projects/000-global/external/ policy, or a web source MUST carry an inline [DOC_ID-CN] citation marker resolving to a Document Register row. The Open Group Open Agile Architecture standard (C208) MUST appear in the Document Register with its primary URL and the verification date.

8. Quality Gate

Before writing the file, read .arckit/references/quality-checklist.md and verify all Common Checks plus the OAAL per-type checks pass. Fix any failures before proceeding.

9. Write the Document

IMPORTANT: The O-AA ADM Lite document will be a substantial document (typically 150-300 lines). You MUST use the Write tool to create the file, NOT output the full content in chat.

Create the file at:

projects/{P}/ARC-{P}-OAAL-v1.0.md

10. Show Summary to User

After writing the file, show a concise summary (NOT the full document):

## O-AA ADM Lite Created

**Document**: `projects/{P}/ARC-{P}-OAAL-v1.0.md`
**Document ID**: ARC-{P}-OAAL-v1.0

### Sprint Plan
| Sprint | TOGAF Phases | Focus | Duration | Deliverable |
|--------|-------------|-------|----------|-------------|
| Sprint 0 | ADM-P + A | Vision + Stakeholders | 1 week | vision.yaml |
| Sprint 1 | ADM-B + C | Business + Data Arch | 2 weeks | business-architecture.yaml |
| Sprint 2 | ADM-C + D | Technology Arch | 2 weeks | technology-architecture.yaml |
| Sprint 3 | ADM-E + F | Implementation | 2 weeks | implementation-strategy.yaml |
| Sprint 4+ | ADM-G + H | Governance | Ongoing | governance-report.yaml |

### Sprint Artifacts
- ✅ vision.yaml (Sprint 0)

- ✅ implementation-strategy.yaml (Sprint 3)

### O-AA Axioms Applied
- [List relevant axioms with brief rationale]

### Synthesised From
- [✅/⚠️] Architecture Principles: ARC-000-PRIN-v[N].md

- [✅/⚠️] ADM Preliminary: ARC-{P}-ADMP-v[N].md

### Next Steps
1. Begin Sprint 0: Stakeholder workshops + vision definition
2. Verify Sprint 0 artefacts: `$arckit-health`
3. Continue to Sprint 1: `$arckit-product-architecture`
4. Plan dual transformation: `$arckit-agile-strategy`

**File location**: `projects/{P}/ARC-{P}-OAAL-v1.0.md`

Important Notes

1. O-AA vs Traditional TOGAF: This is a lightweight, sprint-driven approach. It preserves TOGAF ADM structure but compresses the timeline and deliverable format. Do not use for regulated engagements requiring full ADM audit trails.

2. Sprint Artefacts: The vision.yaml and implementation-strategy.yaml structures are defined inline in oaa-adm-lite-template.md. Validate artefacts against those structures and via $arckit-health; they stay consistent with the traditional TOGAF commands without sharing schema files.

3. Product-Centric: O-AA mandates product-centric architecture (Axiom 15, Project to Product Shift). The organizing principle is the product, not capabilities or services.

4. Use Write Tool: The O-AA ADM Lite document is typically 150-300 lines. ALWAYS use the Write tool to create it.

5. Version Management: If an O-AA ADM Lite document already exists (ARC-*-OAAL-v*.md), create a new version (v2.0) rather than overwriting.

6. Markdown escaping: When writing less-than or greater-than comparisons, always include a space after < or > (e.g., < 3 seconds, > 99.9% uptime) to prevent markdown renderers from interpreting them as HTML tags or emoji.

Suggested Next Steps

After completing this command, consider running:

• $arckit-product-architecture -- Design product-centric architecture for the target product
• $arckit-agile-strategy -- Plan dual transformation with agile strategy canvas
• $arckit-agile-security -- Embed security into the sprint rhythm
• $arckit-agile-governance -- Establish governance cadence for the programme