aiwg 2026.2.10 → 2026.2.12

package/CLAUDE.md

@@ -38,7 +38,7 @@ src/                         # CLI and MCP server implementation
 test/                        # Test suites and fixtures
 tools/                       # Build and deployment scripts
 docs/                        # Documentation
-├── cli-reference.md         # All 40 CLI commands
+├── cli-reference.md         # All 42 CLI commands
 ├── extensions/              # Extension system docs
 │   ├── overview.md
 │   ├── creating-extensions.md
@@ -127,7 +127,7 @@ aiwg new my-project    # Scaffold new project
 aiwg help              # Show all commands
 aiwg doctor            # Check installation health
 
-# See @docs/cli-reference.md for all 40 commands
+# See @docs/cli-reference.md for all 42 commands
 ```
 
 ## Project Artifacts (.aiwg/)
@@ -176,9 +176,9 @@ AIWG uses a unified extension system for all extension types:
 - `@docs/extensions/creating-extensions.md` - Build custom extensions
 - `@docs/extensions/extension-types.md` - Complete type reference
 - `@src/extensions/types.ts` - TypeScript type definitions
-- `@src/extensions/commands/definitions.ts` - All 40 command definitions
+- `@src/extensions/commands/definitions.ts` - All 42 command definitions
 
-## CLI Commands (40 Total)
+## CLI Commands (42 Total)
 
 **See `@docs/cli-reference.md` for complete documentation.**
 
@@ -198,6 +198,8 @@ AIWG uses a unified extension system for all extension types:
 | **Scaffolding** (7) | add-agent, add-command, add-skill, add-template, scaffold-addon, scaffold-extension, scaffold-framework |
 | **Ralph** (4) | ralph, ralph-status, ralph-abort, ralph-resume |
 | **Metrics** (3) | cost-report, cost-history, metrics-tokens |
+| **Documentation** (1) | doc-sync |
+| **SDLC Orchestration** (1) | sdlc-accelerate |
 | **Reproducibility** (4) | execution-mode, snapshot, checkpoint, reproducibility-validate |
 
 ### Quick Reference
@@ -245,6 +247,16 @@ aiwg cost-report             # Show cost report for session
 aiwg cost-history            # Show historical cost data
 aiwg metrics-tokens          # Show token usage metrics
 
+# Documentation sync
+aiwg doc-sync code-to-docs --dry-run  # Audit doc drift
+aiwg doc-sync code-to-docs            # Sync docs to match code
+aiwg doc-sync full --interactive      # Bidirectional reconciliation
+
+# SDLC accelerate
+aiwg sdlc-accelerate "Project description"  # Idea to construction-ready
+aiwg sdlc-accelerate --from-codebase .      # From existing code
+aiwg sdlc-accelerate --resume               # Resume pipeline
+
 # Reproducibility
 aiwg execution-mode          # Show/set execution mode
 aiwg snapshot                # Create execution snapshot
@@ -450,9 +462,9 @@ Before pushing a version tag:
    - Migration notes (if applicable)
    - Links to relevant documentation
 4. **Commit and tag** - `git tag -m "vX.X.X" vX.X.X`
-5. **Push to both remotes** - `git push origin main --tags && git push github main --tags`
-6. **Update GitHub Release** - Add proper release notes via `gh release edit`
-7. **Create Gitea Release** - Via MCP tool or web UI
+5. **Push tag to Gitea** - `git push origin main --tags` (automatically creates Gitea Release)
+6. **Optionally mirror to GitHub** - `git push github main --tags`
+7. **Update/Create GitHub Release manually** - via `gh release create|edit`
 
 ### Version Format
 

package/agentic/code/addons/security/README.md

@@ -123,7 +123,7 @@ Before deploying any code that uses tokens:
 
 Planned additions to this addon:
 
-- Vault integration patterns (HashiCorp Vault, AWS Secrets Manager)
+- Secrets management integration (AWS Secrets Manager, Azure Key Vault)
 - Certificate-based authentication
 - OAuth flow patterns
 - OIDC integration

package/agentic/code/frameworks/sdlc-complete/add-ons/legal/templates/contract-requirements-traceability-matrix.md

@@ -228,7 +228,7 @@ Section 2 establishes traceability framework; Section 3 maps customer contract o
 
 | Contract Clause | System Requirement | Design Decision | Implementation Artifact | Verification Method | Status | Evidence |
 | --- | --- | --- | --- | --- | --- | --- |
-| CL-CONT-2024-001-7.1 | NFR-040: EU data residency | ARCH-040: Regional data isolation (EU data in eu-central-1) | COMP-REGION-001: AWS resources deployed in eu-central-1 | VER-REGION-001: Infrastructure audit | Complete | VER-2024-Q3-030: Terraform config confirms eu-central-1 |
+| CL-CONT-2024-001-7.1 | NFR-040: EU data residency | ARCH-040: Regional data isolation (EU data in eu-central-1) | COMP-REGION-001: AWS resources deployed in eu-central-1 | VER-REGION-001: Infrastructure audit | Complete | VER-2024-Q3-030: IaC config confirms eu-central-1 |
 | CL-CONT-2024-001-7.1 | NFR-041: SCCs for cross-border transfers | ARCH-041: Standard Contractual Clauses with US support team | COMP-SCC-001: SCCs signed | VER-SCC-001: Legal review confirms SCC compliance | Complete | VER-2024-Q3-031: SCCs signed Feb 1, 2024 |
 
 ## 4 Vendor Contract Dependencies Traceability

package/agentic/code/frameworks/sdlc-complete/add-ons/legal/templates/data-sovereignty-template.md

@@ -380,7 +380,7 @@ Section 2 identifies data residency requirements; Section 3 maps data to regions
 - **Bucket region**: [Region ID]
 - **Replication**: [Disabled / Same-region only / Cross-region with encryption]
 
-**Compliance Verification**: Infrastructure-as-Code (Terraform, CloudFormation) enforces regional constraints
+**Compliance Verification**: Infrastructure-as-Code (IaC tools, CloudFormation) enforces regional constraints
 
 #### 5.1.2 Data Residency Enforcement
 

package/agentic/code/frameworks/sdlc-complete/agents/cloud-architect.md

@@ -1,6 +1,6 @@
 ---
 name: Cloud Architect
-description: Multi-cloud infrastructure design specialist. Design AWS/Azure/GCP infrastructure, implement Terraform IaC, optimize costs, handle auto-scaling and multi-region deployments. Use proactively for cloud infrastructure or migration planning
+description: Multi-cloud infrastructure design specialist. Design AWS/Azure/GCP infrastructure, implement infrastructure as code (IaC), optimize costs, handle auto-scaling and multi-region deployments. Use proactively for cloud infrastructure or migration planning
 model: opus
 memory: user
 tools: Bash, Read, Write, MultiEdit, WebFetch
@@ -20,7 +20,7 @@ You are a cloud architect specializing in scalable, cost-effective cloud infrast
 - Plan multi-region strategy
 
 ### Construction Phase
-- Implement Infrastructure as Code (Terraform)
+- Implement Infrastructure as Code (IaC)
 - Configure auto-scaling and load balancing
 - Set up CI/CD pipelines
 - Implement monitoring and alerting
@@ -54,7 +54,7 @@ You are a cloud architect specializing in scalable, cost-effective cloud infrast
 - Design security layers
 
 ### 3. Infrastructure as Code
-- Create Terraform modules
+- Create IaC modules
 - Organize state management
 - Implement environment separation
 - Version control infrastructure
@@ -86,7 +86,7 @@ You are a cloud architect specializing in scalable, cost-effective cloud infrast
 ### High Availability Architecture
 
 ```hcl
-# Terraform: Multi-AZ deployment
+# IaC: Multi-AZ deployment
 resource "aws_instance" "app" {
   count             = 3
   ami               = var.app_ami
@@ -393,7 +393,7 @@ resource "aws_cloudwatch_metric_alarm" "cost_anomaly" {
 For each cloud architecture engagement:
 
 1. **Architecture Diagrams** - Multi-region topology, network design, security layers
-2. **Terraform Modules** - Complete IaC implementation with state management
+2. **IaC Modules** - Complete infrastructure-as-code implementation with state management
 3. **Cost Estimation** - Monthly cost breakdown, ROI analysis, optimization opportunities
 4. **Auto-Scaling Policies** - CPU, memory, request-based scaling configurations
 5. **Security Configuration** - IAM policies, security groups, encryption settings

package/agentic/code/frameworks/sdlc-complete/agents/devops-engineer.md

@@ -113,12 +113,12 @@ jobs:
 
 ## Infrastructure as Code
 
-### Terraform Configuration
+### IaC Configuration
 
 ```hcl
 # AWS EKS Cluster
 module "eks" {
-  source  = "terraform-aws-modules/eks/aws"
+  source  = "registry/aws-modules/eks/aws"
   version = "~> 19.0"
 
   cluster_name    = "production-cluster"
@@ -485,7 +485,7 @@ locals {
     Team        = var.team
     CostCenter  = var.cost_center
     Project     = var.project
-    ManagedBy   = "Terraform"
+    ManagedBy   = "IaC"
   }
 }
 ```

package/agentic/code/frameworks/sdlc-complete/agents/security-auditor.md

@@ -865,7 +865,7 @@ const JWT_SECRETS = {
 
 **Immediate Actions:**
 1. Generate new secret: `openssl rand -hex 64`
-2. Store in environment variable management system (AWS Secrets Manager, HashiCorp Vault)
+2. Store in environment variable management system (AWS Secrets Manager, Azure Key Vault)
 3. Deploy updated code
 4. Invalidate all existing tokens (force re-login)
 5. Remove secret from git history: `git filter-branch` or BFG Repo-Cleaner

package/agentic/code/frameworks/sdlc-complete/commands/doc-sync.md

@@ -0,0 +1,192 @@
+---
+description: Synchronize documentation and code to eliminate drift with parallel audit, auto-fix, and Ralph refinement
+category: documentation
+argument-hint: <direction> [--interactive --guidance "text" --scope "path" --dry-run --parallel N --incremental --verbose --no-commit --max-iterations N]
+allowed-tools: Task, Read, Write, Bash, Glob, Grep, Edit
+model: opus
+---
+
+# Documentation-Code Sync (doc-sync)
+
+You are a Documentation Synchronization Orchestrator that detects and resolves drift between code and documentation through parallel audit, automated fixes, and iterative refinement.
+
+## Your Task
+
+When invoked with `/doc-sync <direction> [options]`:
+
+1. **Parse direction**: `code-to-docs` (code is truth), `docs-to-code` (docs are truth), or `full` (bidirectional reconciliation)
+2. **Audit** code and documentation in parallel for inconsistencies
+3. **Report** drift findings with severity and fix classification
+4. **Fix** auto-fixable issues and iterate on complex ones
+5. **Validate** all changes pass cross-reference checks
+
+## Switches
+
+| Switch | Default | Purpose |
+|--------|---------|---------|
+| `<direction>` | required | `code-to-docs`, `docs-to-code`, `full` |
+| `--interactive` | false | Prompt for each sync decision |
+| `--guidance "text"` | none | Human guidance for ambiguous cases |
+| `--scope "path"` | `.` | Limit to specific directory |
+| `--dry-run` | false | Audit only, no modifications |
+| `--parallel N` | 4 | Max concurrent audit agents |
+| `--incremental` | false | Git-diff since last sync instead of full scan |
+| `--verbose` | false | Detailed per-file findings |
+| `--no-commit` | false | Skip auto-commit |
+| `--max-iterations N` | 3 | Ralph refinement iterations |
+
+## Execution Phases
+
+### Phase 1 — Init
+
+1. Parse direction argument
+2. Validate `--scope` path exists
+3. Read `.aiwg/.last-doc-sync` for incremental mode (skip if not found)
+4. Inventory files in scope:
+   - Count documentation files (`docs/`, `*.md` in root, CLAUDE.md)
+   - Count source files (`src/`, `agentic/`, `tools/`)
+5. If >50 files, activate RLM mode for context management
+
+### Phase 2 — Parallel Audit (Wave 1)
+
+Dispatch 8 domain-specific auditor agents via `parallel-dispatch`:
+
+| Auditor | Docs Scope | Code Scope |
+|---------|-----------|------------|
+| cli-ref-auditor | `docs/cli-reference.md`, CLAUDE.md | `definitions.ts`, `.claude/commands/` |
+| extension-type-auditor | `docs/extensions/` | `src/extensions/types.ts`, `registry.ts` |
+| provider-auditor | `docs/integrations/`, CLAUDE.md provider table | `providers/*.mjs`, `platform-paths.ts` |
+| skill-auditor | `docs/development/skill-inventory.md` | `.claude/skills/`, framework skills |
+| agent-auditor | Agent catalog docs | `agentic/*/agents/` |
+| config-auditor | Config guides | `src/`, `agentic/*/config/` |
+| readme-auditor | `README.md` | `package.json`, `src/` |
+| changelog-auditor | `CHANGELOG.md`, `docs/releases/` | git tags, `package.json` |
+
+Each auditor:
+- Reads its docs scope and code scope
+- Identifies mismatches (missing entries, wrong counts, stale descriptions, dead references)
+- Outputs structured findings as `DOC-DRIFT-NNN` items with severity (critical/high/medium/low)
+
+### Phase 3 — Cross-Reference Audit (Wave 2)
+
+Depends on Wave 1 completion. Run in parallel:
+
+1. **mention-validate**: Check all @-mentions resolve to existing files
+2. **claims-validator**: Verify numeric claims (command counts, agent counts, file counts) against actual counts
+3. **check-traceability**: Verify bidirectional links between artifacts
+4. **Internal link checker**: Validate all markdown links point to existing targets
+
+### Phase 4 — Drift Report
+
+Synthesizer agent produces `.aiwg/reports/doc-sync-audit-{date}.md`:
+
+- **Executive summary**: Total drift items, severity distribution, estimated fix effort
+- **Per-domain findings**: Grouped by auditor, each with DOC-DRIFT-NNN identifier
+- **Cross-reference issues**: Broken links, stale mentions, wrong counts
+- **Sync plan**: Categorized as auto-fixable / template-fixable / human-required
+
+### Phase 5 — Sync Planning
+
+Categorize each drift item:
+
+| Category | Criteria | Action |
+|----------|----------|--------|
+| Auto-fixable | Numeric claims, table entries, argument hints | Direct edit |
+| Template-fixable | Missing sections, outdated descriptions | Generate via template + Ralph |
+| Human-required | Architectural changes, ambiguous intent | Flag for review |
+
+If `--dry-run`: Output report and exit.
+
+### Phase 6 — Auto-fix (code-to-docs direction)
+
+Apply auto-fixes:
+- Update numeric claims (command count, agent count) from source-of-truth
+- Add missing table entries (new commands, new agents)
+- Remove entries for deleted artifacts
+- Update argument hints from `definitions.ts` metadata
+- Fix broken internal links
+
+### Phase 7 — Ralph Refinement
+
+For template-fixable items:
+1. Generate initial fix from template
+2. Run validation (Wave 2 checks) on modified files
+3. If issues remain, iterate (up to `--max-iterations`)
+4. Select best output per best-output-selection rule
+
+### Phase 8 — Validation
+
+Re-run Wave 2 checks on all modified files:
+- All @-mentions resolve
+- Numeric claims match actuals
+- Internal links valid
+- No new drift introduced
+
+### Phase 9 — Record
+
+1. Write `.aiwg/.last-doc-sync` with timestamp and scope
+2. If not `--no-commit`: Stage changes and commit with message `docs: sync documentation to match code`
+3. Output final summary with before/after drift counts
+
+## Direction Behavior
+
+### code-to-docs (Default)
+Code is source of truth. Documentation is updated to match code reality.
+
+### docs-to-code
+Documentation is source of truth. Generates TODOs and code fix suggestions where code doesn't match documented behavior.
+
+### full
+Bidirectional reconciliation:
+1. Run both directions
+2. For conflicts (code says X, docs say Y, both changed), flag for human resolution
+3. In `--interactive` mode, prompt for each conflict
+
+## Integration Points
+
+Uses existing skills and commands:
+- `claims-validator` — Verify numeric claims
+- `mention-validate` — Check @-mention resolution
+- `mention-wire` — Fix broken @-mentions
+- `check-traceability` — Verify bidirectional links
+- `parallel-dispatch` — Launch audit agents concurrently
+- `rlm-mode` — Context management for large file sets
+- `ralph` — Iterative refinement loop
+- `workspace-health` — Pre-flight workspace checks
+
+## Examples
+
+### Dry-run audit
+```
+/doc-sync code-to-docs --dry-run
+```
+Outputs audit report without modifying any files.
+
+### Incremental sync after code changes
+```
+/doc-sync code-to-docs --incremental --verbose
+```
+Only audits files changed since last sync.
+
+### Full bidirectional with human guidance
+```
+/doc-sync full --interactive --guidance "Focus on CLI reference accuracy"
+```
+
+### Scoped to specific directory
+```
+/doc-sync code-to-docs --scope docs/extensions/
+```
+
+## Output Locations
+
+- Audit report: `.aiwg/reports/doc-sync-audit-{date}.md`
+- Last sync record: `.aiwg/.last-doc-sync`
+- Modified documentation: in-place updates
+
+## References
+
+- @src/extensions/commands/definitions.ts — Command definitions source of truth
+- @docs/cli-reference.md — CLI reference documentation
+- @CLAUDE.md — Project-level documentation
+- @agentic/code/frameworks/sdlc-complete/skills/manifest.json — Skills catalog

package/agentic/code/frameworks/sdlc-complete/commands/sdlc-accelerate.md

@@ -0,0 +1,227 @@
+---
+description: End-to-end SDLC ramp-up from idea to construction-ready with automated phase transitions and focused gate questions
+category: sdlc-orchestration
+argument-hint: <description> [--from-codebase <path> --interactive --guidance "text" --auto --dry-run --skip-to <phase> --resume]
+allowed-tools: Task, Read, Write, Glob, TodoWrite
+model: opus
+---
+
+# SDLC Accelerate
+
+You are an SDLC Pipeline Orchestrator that takes a user from idea (or existing codebase) to construction-ready, orchestrating the full pipeline: intake → inception → gate → elaboration → gate → construction prep. You ask focused questions at each gate rather than requiring manual invocation of 7+ commands.
+
+## Your Task
+
+When invoked with `/sdlc-accelerate <description> [options]`:
+
+1. **Detect entry point** from arguments and workspace state
+2. **Execute pipeline** as a state machine through all phases
+3. **Handle gates** with focused questions instead of manual workflows
+4. **Track state** for resume capability
+5. **Produce** a Construction Ready Brief at completion
+
+## Switches
+
+| Switch | Default | Purpose |
+|--------|---------|---------|
+| `<description>` | positional | Project description (idea entry) |
+| `--from-codebase <path>` | none | Scan existing code instead of starting from idea |
+| `--interactive` | false | Full interactive mode at every step |
+| `--guidance "text"` | none | Project-level guidance for all phases |
+| `--auto` | false | Auto-proceed on CONDITIONAL gates |
+| `--dry-run` | false | Show pipeline plan without executing |
+| `--skip-to <phase>` | none | Jump to specific phase (validates prereqs) |
+| `--resume` | false | Resume from detected current phase |
+
+## Entry Point Detection
+
+1. No `.aiwg/` + description provided → `intake-wizard` path
+2. No `.aiwg/` + `--from-codebase` → `intake-from-codebase` path
+3. `.aiwg/` exists + `--resume` → detect phase via `project-status` logic, resume from next incomplete phase
+4. `--skip-to` → validate prerequisites exist, jump to specified phase
+
+## State Machine
+
+```
+INTAKE → GATE_LOM → INCEPTION_TO_ELABORATION → GATE_ABM →
+ELABORATION_TO_CONSTRUCTION → CONSTRUCTION_READY_BRIEF
+```
+
+### Phase 1 — Intake
+
+**Entry**: New project or existing codebase scan
+
+1. If description provided (no `--from-codebase`):
+   - Delegate to `/intake-wizard "<description>"`
+   - Then invoke `/flow-concept-to-inception`
+2. If `--from-codebase`:
+   - Delegate to `/intake-from-codebase --path <path>`
+   - Then invoke `/flow-concept-to-inception`
+3. **Mini-gate**: Present project summary for confirmation:
+   - Project name and type
+   - Detected complexity
+   - Key requirements identified
+   - Confirm or adjust before proceeding
+
+Record phase completion in state file.
+
+### Phase 2 — LOM Gate (Lifecycle Objective Milestone)
+
+Invoke `/flow-gate-check inception`:
+
+- **PASS**: Auto-proceed to elaboration
+- **CONDITIONAL**: Ask 2-3 focused questions:
+  1. "The gate found [specific gap]. Do you want to: (a) address it now, (b) proceed with waiver, (c) abort?"
+  2. If metrics misaligned: "Expected [X], found [Y]. Adjust target or document exception?"
+  3. If risks insufficient: "Only [N] risks identified. Add more or proceed?"
+- **FAIL**: Offer three options:
+  1. Auto-remediate (re-run relevant intake steps)
+  2. Skip with documented waiver
+  3. Abort pipeline
+
+Record gate decision and any waivers in state file.
+
+### Phase 3 — Elaboration
+
+Delegate to `/flow-inception-to-elaboration`.
+
+**ABM Gate** (Architecture Baseline Milestone):
+- Invoke `/flow-gate-check elaboration`
+- On CONDITIONAL, ask focused questions:
+  1. "ADR [name] needs review — approve, revise, or skip?"
+  2. "Test coverage target is [X%]. Confirm or adjust?"
+  3. "Risk retirement at [N%] vs [target%]. Address or waive?"
+
+Record phase completion and gate decisions.
+
+### Phase 4 — Construction Prep
+
+Delegate to `/flow-elaboration-to-construction`.
+
+**Final mini-gate**:
+1. Present iteration 1 scope summary
+2. Confirm ready to build
+3. Flag any open items that need resolution
+
+### Phase 5 — Construction Ready Brief
+
+Generate consolidated `.aiwg/reports/construction-ready-brief.md` using template:
+
+Contents:
+- **Gate Decision Log**: All gate results, waivers, and decisions
+- **Artifacts Produced**: Complete list with status (draft/approved/baselined)
+- **Architecture Summary**: Key ADRs and architecture decisions
+- **Iteration Plans**: First 2-3 iterations scoped
+- **Open Items**: Anything deferred or waived
+- **Next Steps**: Immediate actions to begin construction
+
+## Resume Support
+
+State tracked in `.aiwg/reports/accelerate-state.json`:
+
+```json
+{
+  "version": "1.0.0",
+  "started": "2026-02-26T10:00:00Z",
+  "description": "Customer portal with real-time chat",
+  "entryPoint": "intake-wizard",
+  "phases": {
+    "intake": { "status": "completed", "completedAt": "...", "artifacts": [...] },
+    "gate_lom": { "status": "completed", "result": "CONDITIONAL", "waivers": [...] },
+    "elaboration": { "status": "in_progress", "startedAt": "..." },
+    "gate_abm": { "status": "pending" },
+    "construction_prep": { "status": "pending" },
+    "brief": { "status": "pending" }
+  },
+  "guidance": "Focus on API-first design",
+  "decisions": [
+    { "phase": "gate_lom", "question": "Proceed with 8 risks?", "answer": "waiver", "timestamp": "..." }
+  ]
+}
+```
+
+`--resume` reads state file, finds next incomplete phase, continues from there.
+
+## Dry Run Behavior
+
+With `--dry-run`:
+1. Detect entry point
+2. Show planned pipeline phases
+3. List commands that would be invoked
+4. Estimate artifact count
+5. Exit without executing
+
+Output format:
+```
+SDLC Accelerate Pipeline Plan
+==============================
+Entry: intake-wizard
+Description: "Customer portal with real-time chat"
+
+Phase 1: Intake
+  → /intake-wizard "Customer portal with real-time chat"
+  → /flow-concept-to-inception
+  Artifacts: intake form, solution profile
+
+Phase 2: LOM Gate
+  → /flow-gate-check inception
+  Artifacts: gate report
+
+Phase 3: Elaboration
+  → /flow-inception-to-elaboration
+  → /flow-gate-check elaboration
+  Artifacts: SAD, ADRs, test strategy, requirements
+
+Phase 4: Construction Prep
+  → /flow-elaboration-to-construction
+  Artifacts: iteration plans, construction backlog
+
+Phase 5: Construction Ready Brief
+  Artifacts: construction-ready-brief.md
+
+Estimated: 15-25 artifacts, 5 phase transitions
+```
+
+## Examples
+
+### New project from idea
+```
+/sdlc-accelerate "Customer portal with real-time chat and payment integration"
+```
+
+### From existing codebase
+```
+/sdlc-accelerate --from-codebase ./src "E-commerce platform"
+```
+
+### Resume interrupted pipeline
+```
+/sdlc-accelerate --resume
+```
+
+### Preview pipeline
+```
+/sdlc-accelerate --dry-run "Mobile banking app"
+```
+
+### Skip to elaboration (prerequisites validated)
+```
+/sdlc-accelerate --skip-to elaboration
+```
+
+## Integration Points
+
+Delegates to existing commands:
+- `/intake-wizard` — Project intake from description
+- `/intake-from-codebase` — Intake from existing code
+- `/flow-concept-to-inception` — Concept to inception transition
+- `/flow-gate-check` — Phase gate evaluation
+- `/flow-inception-to-elaboration` — Inception to elaboration
+- `/flow-elaboration-to-construction` — Elaboration to construction
+- `/project-status` — Current phase detection for resume
+
+## References
+
+- @agentic/code/frameworks/sdlc-complete/schemas/flows/accelerate-state.yaml
+- @agentic/code/frameworks/sdlc-complete/templates/management/construction-ready-brief-template.md
+- @agentic/code/frameworks/sdlc-complete/skills/sdlc-accelerate/SKILL.md

package/agentic/code/frameworks/sdlc-complete/docs/token-security.md

@@ -72,7 +72,7 @@ curl -s -H "Authorization: token $(cat ~/.config/gitea/token)" \
 
 ### 3. Vault Integration (Future)
 
-Reserved for enterprise deployments with HashiCorp Vault or similar.
+Reserved for enterprise deployments with a secrets manager or similar.
 
 ```bash
 # Future pattern (not yet implemented)