Add cross-functional Archon workflow templates

.archon/commands/design/design-brief.md

@@ -0,0 +1,55 @@
+---
+description: Convert an approved PRD into a design brief and UX handoff plan
+argument-hint: <prd path or feature description>
+---
+
+# Design Brief
+
+**Input**: $ARGUMENTS
+
+---
+
+## Mission
+
+Create a design brief that gives implementation and QA enough context to build and validate the user experience.
+
+## Process
+
+1. Read `$ARTIFACTS_DIR/product/prd.md` if present.
+2. Inspect existing UI patterns, components, routes, and accessibility conventions.
+3. Identify required user flows, states, copy, errors, empty states, and permissions.
+4. Write `$ARTIFACTS_DIR/design/design-brief.md`.
+
+## Artifact Format
+
+```markdown
+# Design Brief
+
+## UX Goal
+
+## Primary User Flow
+
+## Secondary Flows
+
+## States
+
+- Loading:
+- Empty:
+- Error:
+- Permission denied:
+- Success:
+
+## Interaction Requirements
+
+## Accessibility Requirements
+
+## Existing Patterns To Reuse
+
+## Open Design Questions
+
+## Handoff Checklist
+```
+
+## Output
+
+Return the artifact path and any design blockers.

.archon/commands/design/design-handoff-check.md

@@ -0,0 +1,42 @@
+---
+description: Verify design handoff completeness before implementation proceeds
+argument-hint: <feature or PRD path>
+---
+
+# Design Handoff Check
+
+**Input**: $ARGUMENTS
+
+---
+
+## Mission
+
+Confirm the design handoff is complete enough for implementation and QA.
+
+## Process
+
+1. Read the PRD and design brief artifacts.
+2. Check for required flows, states, acceptance notes, copy, and accessibility expectations.
+3. Write `$ARTIFACTS_DIR/design/handoff.md`.
+
+## Artifact Format
+
+```markdown
+# Design Handoff
+
+## Status
+
+Ready / Ready with caveats / Blocked
+
+## Required Implementation Notes
+
+## Required QA Notes
+
+## Missing Design Inputs
+
+## Approval Recommendation
+```
+
+## Output
+
+Return the handoff status and artifact path.

.archon/commands/design/design-ui-review.md

@@ -0,0 +1,48 @@
+---
+description: Review a PR or implementation against design and UX expectations
+argument-hint: <PR number, branch, or implementation summary>
+---
+
+# Design UI Review
+
+**Input**: $ARGUMENTS
+
+---
+
+## Mission
+
+Review the implementation for design consistency, accessibility, and user-flow quality.
+
+## Process
+
+1. Read `$ARTIFACTS_DIR/design/design-brief.md` and `$ARTIFACTS_DIR/development/implementation-report.md` if present.
+2. Inspect changed UI files and any screenshots or validation artifacts.
+3. Compare implementation against existing UI patterns.
+4. Write `$ARTIFACTS_DIR/design/ux-review.md`.
+
+## Artifact Format
+
+```markdown
+# UX Review
+
+## Verdict
+
+Pass / Pass with follow-ups / Blocked
+
+## Findings
+
+| Severity | Area | Finding | Required Action |
+|----------|------|---------|-----------------|
+
+## Accessibility Notes
+
+## Visual Consistency Notes
+
+## User Flow Notes
+
+## Approval Recommendation
+```
+
+## Output
+
+Return the verdict and artifact path.

.archon/commands/development/development-confirm-plan.md

@@ -0,0 +1,50 @@
+---
+description: Confirm that an approved PRD or implementation plan is ready to build
+argument-hint: <prd path, plan path, issue, or feature request>
+---
+
+# Development Confirm Plan
+
+**Input**: $ARGUMENTS
+
+---
+
+## Mission
+
+Confirm the implementation scope before code changes begin.
+
+## Process
+
+1. Read product, design, and security artifacts if present.
+2. Inspect the repo for relevant files, APIs, tests, and patterns.
+3. Identify the smallest safe implementation path.
+4. Write `$ARTIFACTS_DIR/development/implementation-plan.md`.
+
+## Artifact Format
+
+```markdown
+# Implementation Plan
+
+## Scope
+
+## Non-Scope
+
+## Files And Modules
+
+| Path | Action | Notes |
+|------|--------|-------|
+
+## Implementation Steps
+
+## Validation Commands
+
+## Risks
+
+## Security Triggers
+
+## Rollback Notes
+```
+
+## Output
+
+Return the plan path and whether implementation is ready.

.archon/commands/development/development-implementation-report.md

@@ -0,0 +1,48 @@
+---
+description: Summarize implementation results for downstream review
+argument-hint: <implementation context>
+---
+
+# Development Implementation Report
+
+**Input**: $ARGUMENTS
+
+---
+
+## Mission
+
+Create an implementation report that downstream QA, security, docs, DevOps, and services workflows can consume.
+
+## Process
+
+1. Inspect git diff and commits.
+2. Read validation output and PR metadata if available.
+3. Write `$ARTIFACTS_DIR/development/implementation-report.md`.
+
+## Artifact Format
+
+```markdown
+# Implementation Report
+
+## Summary
+
+## Changed Files
+
+## Behavior Changes
+
+## Validation Evidence
+
+## Known Limitations
+
+## Security-Relevant Changes
+
+## QA Notes
+
+## Docs Impact
+
+## Rollback Notes
+```
+
+## Output
+
+Return the report path and any downstream blockers.

.archon/commands/devops/devops-deployment-readiness.md

@@ -0,0 +1,46 @@
+---
+description: Review deployment readiness, operational risk, and production prerequisites
+argument-hint: <release candidate, PR, or implementation report>
+---
+
+# DevOps Deployment Readiness
+
+**Input**: $ARGUMENTS
+
+---
+
+## Mission
+
+Determine whether the change is ready to deploy safely.
+
+## Process
+
+1. Read product, development, QA, security, and docs artifacts if present.
+2. Inspect migrations, configuration, env vars, infrastructure, CI, release scripts, and rollback paths.
+3. Write `$ARTIFACTS_DIR/devops/deployment-plan.md`.
+
+## Artifact Format
+
+```markdown
+# Deployment Readiness
+
+## Verdict
+
+Ready / Ready with caveats / Blocked
+
+## Deployment Steps
+
+## Required Config Or Secrets
+
+## Migration Notes
+
+## Monitoring And Alerts
+
+## Rollback Readiness
+
+## Blockers
+```
+
+## Output
+
+Return the verdict and artifact path.

.archon/commands/devops/devops-incident-followup.md

@@ -0,0 +1,44 @@
+---
+description: Convert incident notes into remediation and runbook updates
+argument-hint: <incident summary or link>
+---
+
+# DevOps Incident Follow-Up
+
+**Input**: $ARGUMENTS
+
+---
+
+## Mission
+
+Convert an incident into actionable remediation, runbook updates, and product follow-up.
+
+## Process
+
+1. Read incident notes from input.
+2. Identify root cause, contributing factors, detection gaps, and prevention tasks.
+3. Write `$ARTIFACTS_DIR/devops/incident-followup.md`.
+
+## Artifact Format
+
+```markdown
+# Incident Follow-Up
+
+## Summary
+
+## Customer Impact
+
+## Root Cause
+
+## Detection And Response Gaps
+
+## Remediation Tasks
+
+## Runbook Updates
+
+## Product Follow-Up
+```
+
+## Output
+
+Return the artifact path and recommended issues to create.

.archon/commands/devops/devops-rollback-plan.md

@@ -0,0 +1,42 @@
+---
+description: Generate a rollback plan for risky releases
+argument-hint: <release candidate or PR>
+---
+
+# DevOps Rollback Plan
+
+**Input**: $ARGUMENTS
+
+---
+
+## Mission
+
+Create a concrete rollback plan for a risky release.
+
+## Process
+
+1. Read deployment, security, QA, and implementation artifacts.
+2. Identify rollback commands, data migration constraints, monitoring signals, and ownership.
+3. Write `$ARTIFACTS_DIR/devops/rollback-plan.md`.
+
+## Artifact Format
+
+```markdown
+# Rollback Plan
+
+## Rollback Trigger
+
+## Fast Rollback Path
+
+## Data Considerations
+
+## Verification After Rollback
+
+## Owner
+
+## Communication Plan
+```
+
+## Output
+
+Return the rollback plan path.