feat: Add Architecture Description (AD) mode with /architect command

Implement Rozanski & Woods methodology for architecture-first development:

New Components:
- /speckit.architect command with 4 actions: init, map, update, review
- 7 viewpoints: Context, Functional, Information, Concurrency, Development, Deployment, Operational
- 2 perspectives: Security, Performance & Scalability
- New 'ad' workflow mode alongside build/spec modes
- Language-agnostic codebase scanning for brownfield projects

Files Added:
- templates/architecture-template.md: Complete R&W template with all viewpoints
- templates/commands/architect.md: Command template with detailed execution phases
- scripts/bash/setup-architecture.sh: Bash implementation with all 4 actions
- scripts/powershell/setup-architecture.ps1: PowerShell equivalent

Files Updated:
- src/specify_cli/__init__.py: Added 'ad' mode configuration
- templates/commands/mode.md: Added AD mode description
- README.md: Added AD workflow documentation and usage examples
- CHANGELOG.md: Added release notes for v0.0.24
- pyproject.toml: Version bump to 0.0.24

Integration:
- AD mode inherits global architecture.md context
- Features validate against architectural boundaries
- Aligns with 12-Factor methodology (Factors I, IX, X)

Author: kanfil

CHANGELOG.md

@@ -7,6 +7,21 @@ All notable changes to the Specify CLI and templates are documented here.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [Unreleased]
+
+### Added
+
+- **Architecture Description (AD) Mode**: New workflow mode for architecture-first development
+  - New `/speckit.architect` command implementing Rozanski & Woods "Software Systems Architecture" methodology
+  - 7 Core Viewpoints: Context, Functional, Information, Concurrency, Development, Deployment, Operational
+  - 2 Cross-cutting Perspectives: Security, Performance & Scalability
+  - Four actions: `init` (greenfield), `map` (brownfield/reverse-engineering), `update` (sync with changes), `review` (validation)
+  - Language-agnostic codebase scanning for brownfield projects
+  - Generates `memory/architecture.md` as central architecture artifact
+  - AD mode added to mode configuration alongside `build` and `spec` modes
+  - Templates: `templates/architecture-template.md` and `templates/commands/architect.md`
+  - Scripts: `scripts/bash/setup-architecture.sh` and `scripts/powershell/setup-architecture.ps1`
+
 ## [0.0.23] - 2025-01-28
 
 ### Changed

README.md

@@ -248,6 +248,7 @@ Specify supports two workflow modes that control the complexity level of the dev
 
 - **`spec` mode (default)**: Full structured specification with comprehensive requirements, research, and validation
 - **`build` mode**: Lightweight, conversational approach focused on quick validation and exploration
+- **`ad` mode**: Architecture-first workflow using Rozanski & Woods methodology for complex enterprise systems
 
 #### Mode Commands
 
@@ -261,6 +262,9 @@ Specify supports two workflow modes that control the complexity level of the dev
 # Switch to spec mode (comprehensive development)
 /mode spec
 
+# Switch to AD mode (architecture-driven development)
+/mode ad
+
 # Show detailed information about all modes
 /mode --info
 ```
@@ -281,6 +285,13 @@ Specify supports two workflow modes that control the complexity level of the dev
 - Production systems needing comprehensive validation
 - When you need full traceability and quality gates
 
+**Use `ad` mode for:**
+
+- Complex enterprise systems requiring formal architecture documentation
+- Brownfield/modernization projects needing existing system mapping
+- Microservices architectures with multiple stakeholders
+- Systems with strict security, performance, or compliance requirements
+
 #### Mode-Aware Commands
 
 All slash commands adapt their behavior based on the current mode:
@@ -302,6 +313,52 @@ specify init my-project \
   --async-agent jules
 ```
 
+### Architecture-Driven Development (AD Mode)
+
+For complex enterprise systems, use Architecture-Driven Development to establish system-level architecture before feature implementation.
+
+#### AD Mode Workflow
+
+```bash
+# 1. Switch to AD mode
+/mode ad
+
+# 2. Initialize architecture (greenfield)
+/speckit.architect init
+
+# 3. Or map existing codebase (brownfield)
+/speckit.architect map
+
+# 4. Review architecture against constitution
+/speckit.architect review
+
+# 5. Then proceed with normal workflow
+/speckit.specify "Feature within this architecture"
+```
+
+#### Architecture Actions
+
+| Action | Description |
+|--------|-------------|
+| `init` | Initialize new `memory/architecture.md` from Rozanski & Woods template |
+| `map` | Reverse-engineer architecture from existing codebase (brownfield) |
+| `update` | Update architecture based on codebase/spec changes with impact analysis |
+| `review` | Validate architecture against constitution and perspectives |
+
+#### Rozanski & Woods Viewpoints
+
+The `/speckit.architect` command generates documentation covering:
+
+1. **Context View** - System scope and external interactions
+2. **Functional View** - Functional elements and responsibilities
+3. **Information View** - Data storage, management, and flow
+4. **Concurrency View** - Runtime processes and coordination
+5. **Development View** - Code organization and CI/CD
+6. **Deployment View** - Physical infrastructure and environments
+7. **Operational View** - Operations, monitoring, and support
+
+Plus cross-cutting **Perspectives**: Security, Performance & Scalability
+
 ### 2. Establish project principles
 
 Launch your AI assistant in the project directory. The `/speckit.*` commands are available in the assistant.
@@ -413,7 +470,7 @@ The `specify` command supports the following options:
 
 | Argument/Option | Type     | Description                                                                 |
 |-----------------|----------|-----------------------------------------------------------------------------|
-| `<mode>`        | Argument | Workflow mode: `build` (lightweight) or `spec` (comprehensive) - leave empty to show current mode |
+| `<mode>`        | Argument | Workflow mode: `build` (lightweight), `spec` (comprehensive), or `ad` (architecture-driven) - leave empty to show current mode |
 | `--tdd/--no-tdd` | Option | Enable/disable TDD (Test-Driven Development) |
 | `--contracts/--no-contracts` | Option | Enable/disable API contract generation |
 | `--data-models/--no-data-models` | Option | Enable/disable data model generation |
@@ -486,6 +543,7 @@ specify check
 /mode                    # Show current mode
 /mode build             # Switch to lightweight build mode
 /mode spec              # Switch to comprehensive spec mode
+/mode ad                # Switch to architecture-driven mode
 /mode --info            # Show detailed mode information
 ```
 
@@ -499,6 +557,7 @@ Essential commands for the Spec-Driven Development workflow:
 
 | Command                  | Description                                                           |
 |--------------------------|-----------------------------------------------------------------------|
+| `/speckit.architect`     | Generate Architecture Description using Rozanski & Woods methodology (7 viewpoints + perspectives) |
 | `/speckit.constitution`  | Create or update project governing principles and development guidelines |
 | `/speckit.specify`       | Define what you want to build (requirements and user stories)        |
 | `/speckit.plan`          | Create technical implementation plans with your chosen tech stack & SYNC/ASYNC triage          |

pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "agentic-sdlc-specify-cli"
-version = "0.0.23"
+version = "0.0.24"
 description = "Specify CLI, part of GitHub Spec Kit. A tool to bootstrap your projects for Spec-Driven Development (SDD)."
 requires-python = ">=3.11"
 dependencies = [