aegis-sdlc 0.1.1__tar.gz

aegis_sdlc-0.1.1/.gitignore

@@ -0,0 +1,29 @@
+# Python
+__pycache__/
+*.py[cod]
+.pytest_cache/
+*.egg-info/
+build/
+dist/
+.venv/
+venv/
+
+# Artifact documents (not tracked)
+# Each application lives in its own subfolder: docs/artifacts/<app-name>/...
+# The whole per-app tree is generated by the agents and is not version-controlled.
+docs/artifacts/*/
+# Keep the multi-application index/router that lists the apps.
+!docs/artifacts/README.md
+
+# Node / mermaid-cli (mmdc) diagram-rendering artifacts
+node_modules/
+puppeteer-config.json
+.vscode/mcp.json
+
+# Claude Code: local MCP config (copy from .mcp.example.json) and personal settings
+.mcp.json
+.claude/settings.local.json
+CLAUDE.local.md
+
+# Local-only denylist of private terms (see scripts/ci/denylist.txt)
+.denylist.local

aegis_sdlc-0.1.1/CHANGELOG.md

@@ -0,0 +1,116 @@
+# Changelog
+
+All notable changes to this project are documented here. The format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and the project uses
+[Semantic Versioning](https://semver.org/spec/v2.0.0.html). Until 1.0.0, minor versions
+may include breaking changes; they are listed under **Changed**.
+
+## [Unreleased]
+
+## [0.1.1] - 2026-09-24
+
+The first release on PyPI (`pip install aegis-sdlc`), and the Claude Code plugin.
+
+### Added
+
+- The CLI is packaged for PyPI as `aegis-sdlc` (the `artifact-tools` command and the
+  `artifact_tools` module keep their names). Publishing a GitHub release publishes the
+  package through Trusted Publishing. CI builds the package and runs the installed CLI
+  outside the repository.
+- **Claude Code plugin (preview).** Install AEGIS into your own repository with
+  `/plugin marketplace add nishant-tamilselvan/AEGIS` and `/plugin install aegis@aegis`.
+  Commands are namespaced (`/aegis:start-ideation`), a `SessionStart` hook loads the
+  golden rules and checks for the `aegis-sdlc` CLI, and the guard runs against your
+  repository. The plugin is generated from `aegis/` and validated in CI with
+  `claude plugin validate --strict`. See
+  [docs/claude-code-plugin.md](docs/claude-code-plugin.md).
+- The guard recognizes namespaced plugin agents (`aegis:service-implementer`) as
+  implementers.
+- Both hook scripts accept `--repo-root`, so they can run from a plugin folder against
+  the user's repository. An empty or missing `--repo-root` value is treated as a guard
+  failure: implementers are denied and other calls need approval.
+
+### Changed
+
+- `check_readiness` moved from `artifact_tools.implementation` to
+  `artifact_tools.readiness`, and `Issue` and `has_errors` moved to
+  `artifact_tools.issues` (`artifact_tools.validate` still re-exports them). This removes
+  the import cycles between the validators. The CLI is unchanged.
+
+### Fixed
+
+- When the implementation target is the same repository that holds `docs/artifacts/`,
+  the guard no longer blocks `artifact-manager` and other non-implementation agents from
+  writing artifacts. Implementers are still denied there, and code writes still require
+  the active package's implementer.
+- An installed CLI used outside an AEGIS clone could not find its templates. The wheel
+  now bundles them; a repository's own templates still take precedence.
+
+## [0.1.0] - 2026-09-24
+
+First public, organization-neutral release, for GitHub Copilot and Claude Code.
+
+### Added
+
+- Three-phase agent system (ideation, architecture and implementation) with 18 agents,
+  10 prompts and 4 skills, for two agent hosts:
+  - **GitHub Copilot in VS Code:** custom agents, prompt files and skills in `.github/`,
+    with hooks in `.github/hooks/`.
+  - **Claude Code:** the 15 specialists as subagents (`.claude/agents/`), the 10 prompts as
+    slash-command skills that run the orchestrators in the main conversation
+    (`.claude/skills/`), hooks in `.claude/settings.json`, and `CLAUDE.md`. See
+    [docs/claude-code.md](docs/claude-code.md).
+- One source for both hosts: agents, prompts, skills and golden rules live in `aegis/`.
+  `scripts/sync_platforms.py` generates the Copilot and Claude Code files, and CI and
+  pre-commit fail when they drift.
+- `artifact_tools` CLI to scaffold, validate and maintain artifacts, ADRs, interface
+  contracts, diagrams and phase-3 implementation state.
+- Implementation guard (`PreToolUse`) and automatic validation (`PostToolUse`) hooks,
+  shared by both hosts. The guard recognizes Copilot agent names and Claude Code subagents
+  (`agent_type`). The validation hook returns feedback as `systemMessage` for Copilot and
+  `additionalContext` for Claude Code (`--platform claude`).
+- A worked example, [`examples/artifacts/todo-list/`](examples/artifacts/): a complete,
+  approved phase 1 and phase 2 artifact set for a simple to-do app, with an OpenAPI 3.1
+  contract and two ADRs. CI keeps it passing strict validation and the readiness gate.
+- Enterprise Standards integration: the `enterprise-standards` skill, a reference MCP
+  server with a sample knowledge base, MCP templates for both hosts
+  (`.vscode/mcp.example.json`, `.mcp.example.json`) and a setup guide.
+- Repository checks for personal paths, denylisted terms, invisible Unicode, workflow
+  security and broken links.
+- CI on Windows, macOS and Linux with SHA-pinned actions, a secret scan, Dependabot and
+  pre-commit hooks.
+- CodeQL code scanning (Python and GitHub Actions) and OpenSSF Scorecard workflows.
+- Community files: security policy, contributing guide, Code of Conduct, issue forms and
+  a pull request template.
+- Golden rules that treat external content as data and forbid copying secrets into
+  artifacts.
+
+### Changed
+
+- The organization-specific playbook integration is now the generic Enterprise
+  Standards library (`enterprise-standards-server`).
+- The `--playbook-review` CLI option and the `playbook_review` pointer field are renamed to
+  `--standards-review` and `standards_review`.
+- The CLI reads templates from `aegis/skills/` instead of `.github/skills/`.
+- Implementation readiness accepts `CLAUDE.md` as a target repository's conventions file.
+
+### Security
+
+- The implementation guard hook never fails open. An agent host lets a tool call proceed
+  when its hook crashes, so on any failure the wrapper denies implementation agents and
+  asks you about every other call. Deny reasons also go to stderr, where Claude Code reads
+  them.
+- Only the active work package's implementation agent may write to the target
+  repository. Writes there from orchestrators, reviewers or the Claude Code main
+  conversation are denied with a reminder to delegate.
+
+### Fixed
+
+- Writing implementation state no longer fails intermittently on Windows when another
+  process briefly holds the file open. The atomic rename now retries.
+- The CLI writes LF line endings on every platform. On Windows, scaffolded artifacts,
+  ADRs, changelog entries and contract stubs were written with CRLF.
+
+[Unreleased]: https://github.com/nishant-tamilselvan/AEGIS/compare/v0.1.1...HEAD
+[0.1.1]: https://github.com/nishant-tamilselvan/AEGIS/compare/v0.1.0...v0.1.1
+[0.1.0]: https://github.com/nishant-tamilselvan/AEGIS/releases/tag/v0.1.0

aegis_sdlc-0.1.1/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 NISHANT TAMILSELVAN
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

aegis_sdlc-0.1.1/PKG-INFO

@@ -0,0 +1,73 @@
+Metadata-Version: 2.5
+Name: aegis-sdlc
+Version: 0.1.1
+Summary: CLI for AEGIS: scaffold, validate and track requirements, architecture artifacts, ADRs and implementation work packages.
+Project-URL: Homepage, https://github.com/nishant-tamilselvan/AEGIS
+Project-URL: Documentation, https://github.com/nishant-tamilselvan/AEGIS/tree/main/docs
+Project-URL: Issues, https://github.com/nishant-tamilselvan/AEGIS/issues
+Project-URL: Changelog, https://github.com/nishant-tamilselvan/AEGIS/blob/main/CHANGELOG.md
+Author: Nishant Tamilselvan
+License: MIT
+License-File: LICENSE
+Keywords: adr,ai-agents,architecture,claude-code,github-copilot,mcp,requirements,sdlc
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Documentation
+Classifier: Topic :: Software Development :: Quality Assurance
+Requires-Python: >=3.10
+Requires-Dist: pyyaml>=6.0
+Provides-Extra: dev
+Requires-Dist: pre-commit>=4.0; extra == 'dev'
+Requires-Dist: pytest>=8.0; extra == 'dev'
+Requires-Dist: ruff>=0.16; extra == 'dev'
+Provides-Extra: diagrams
+Requires-Dist: mermaidx>=0.8; extra == 'diagrams'
+Description-Content-Type: text/markdown
+
+# aegis-sdlc
+
+The command-line tool behind [AEGIS](https://github.com/nishant-tamilselvan/AEGIS), a set
+of agents for GitHub Copilot and Claude Code that turn an idea into approved
+requirements, an implementable architecture and reviewed code.
+
+The agents call this CLI to keep their documents consistent. You can also use it on its
+own, for example in CI, to scaffold and validate AEGIS artifacts.
+
+## Install
+
+```bash
+pip install aegis-sdlc
+```
+
+This installs the `artifact-tools` command. Python 3.10 or later is required.
+
+## Use
+
+```bash
+artifact-tools scaffold product-requirements docs/artifacts/my-app --project "My App"
+artifact-tools validate docs/artifacts/my-app --strict
+artifact-tools adr new "Use PostgreSQL" docs/artifacts/my-app/architecture-decisions --status accepted
+artifact-tools implementation readiness docs/artifacts/my-app /path/to/target-repo
+```
+
+The artifact and implementation templates are bundled with the package. Inside a
+repository that has its own `aegis/skills/.../templates` folders, those are used instead,
+so customized templates keep working.
+
+## Learn more
+
+- [AEGIS on GitHub](https://github.com/nishant-tamilselvan/AEGIS): the agents, prompts
+  and skills for GitHub Copilot and Claude Code.
+- [CLI reference](https://github.com/nishant-tamilselvan/AEGIS/blob/main/docs/cli-reference.md)
+- [A complete example](https://github.com/nishant-tamilselvan/AEGIS/tree/main/examples/artifacts)
+- [Changelog](https://github.com/nishant-tamilselvan/AEGIS/blob/main/CHANGELOG.md)
+
+MIT licensed.

aegis_sdlc-0.1.1/README.md

@@ -0,0 +1,132 @@
+<p align="center">
+  <img src="assets/aegis-logo.svg" alt="AEGIS" width="360" />
+</p>
+
+<p align="center">
+  <strong>Agentic Enterprise Guided Intelligent System</strong><br />
+  From a one-line idea to approved requirements, an implementable architecture and reviewed code, inside VS Code or Claude Code.
+</p>
+
+<p align="center">
+  <a href="https://github.com/nishant-tamilselvan/AEGIS/actions/workflows/ci.yml"><img src="https://github.com/nishant-tamilselvan/AEGIS/actions/workflows/ci.yml/badge.svg?branch=main" alt="CI" /></a>
+  <a href="https://github.com/nishant-tamilselvan/AEGIS/actions/workflows/codeql.yml"><img src="https://github.com/nishant-tamilselvan/AEGIS/actions/workflows/codeql.yml/badge.svg?branch=main" alt="CodeQL" /></a>
+  <a href="https://scorecard.dev/viewer/?uri=github.com/nishant-tamilselvan/AEGIS"><img src="https://api.scorecard.dev/projects/github.com/nishant-tamilselvan/AEGIS/badge" alt="OpenSSF Scorecard" /></a>
+  <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-blue.svg" alt="MIT license" /></a>
+  <img src="https://img.shields.io/badge/python-3.10%2B-3776AB?logo=python&amp;logoColor=white" alt="Python 3.10+" />
+  <img src="https://img.shields.io/badge/VS%20Code-Copilot%20agents-007ACC?logo=visualstudiocode&amp;logoColor=white" alt="VS Code Copilot agents" />
+  <img src="https://img.shields.io/badge/Claude%20Code-subagents%20%2B%20skills-D97757?logo=claude&amp;logoColor=white" alt="Claude Code subagents and skills" />
+  <img src="https://img.shields.io/badge/MCP-Enterprise%20Standards-6E56CF" alt="MCP Enterprise Standards" />
+</p>
+
+<p align="center">
+  <a href="docs/getting-started.md">Getting started</a> ·
+  <a href="docs/claude-code.md">Claude Code</a> ·
+  <a href="docs/how-it-works.md">How it works</a> ·
+  <a href="docs/agents.md">Agents</a> ·
+  <a href="docs/cli-reference.md">CLI</a> ·
+  <a href="docs/enterprise-standards-setup.md">Enterprise Standards</a> ·
+  <a href="docs/troubleshooting.md">Troubleshooting</a>
+</p>
+
+---
+
+AEGIS is a set of agents, prompts and skills for GitHub Copilot in VS Code and for Claude
+Code, backed by a Python tool layer. Orchestrator agents guide you one small step at a time. Specialist agents write
+and maintain a set of living documents. The tooling validates those documents after every
+change, so requirements, architecture and code stay consistent.
+
+## Why AEGIS
+
+- **One step at a time.** Orchestrators ask a few focused questions, recap and wait for you.
+  You never get a 40-question form.
+- **Documents that stay consistent.** Every artifact uses a fixed template and stable ids.
+  Validation runs after each edit, and a critic agent fixes what it finds.
+- **Grounded in your standards.** Agents check your organization's Enterprise Standards
+  first, cite them, and ask only about what they leave open.
+- **Bounded, reviewed implementation.** Code is written one approved work package at a time,
+  inside declared paths, and completes only with an independent review and recorded evidence.
+- **No automatic deployment.** Release needs a named human approver.
+
+## Quick start
+
+```bash
+git clone https://github.com/nishant-tamilselvan/AEGIS.git && cd AEGIS
+pip install -e .
+```
+
+Then open it in your agent host:
+
+| GitHub Copilot | Claude Code |
+| --- | --- |
+| Open the folder in VS Code and switch Copilot Chat to Agent mode. | Run `claude` in the folder. See [Using AEGIS with Claude Code](docs/claude-code.md). Or install AEGIS into your own repository [as a plugin](docs/claude-code-plugin.md) (preview). |
+
+Start with the same command on either platform:
+
+```text
+/start-ideation customer-portal A self-service portal where customers track orders
+```
+
+When ideation is done, continue with `/start-architecture customer-portal`, then
+`/start-implementation customer-portal <absolute-path-to-target-repo>`.
+The [getting started guide](docs/getting-started.md) walks through each phase.
+
+## How it works
+
+```mermaid
+flowchart LR
+    U[Raw idea] --> P1[1. Ideation<br/>6 business artifacts]
+    P1 --> P2[2. Architecture<br/>5 technical artifacts + ADRs]
+    P2 --> G{Readiness gate}
+    G -- blocked --> P2
+    G -- ready --> P3[3. Implementation<br/>bounded work packages]
+    P3 --> R[Independent review<br/>+ evidence]
+    R --> H[Human release approval]
+```
+
+| Phase | You get |
+| --- | --- |
+| **Ideation** | Product, functional and non-functional requirements, a user journey map, a system blueprint and an executive briefing. |
+| **Architecture** | Interface specifications with native contracts, data, security, deployment and observability architecture, and ADRs. |
+| **Implementation** | Work packages traced to the artifacts, a decision ledger, and reviewed code in your target repository. |
+
+Artifacts live in `docs/artifacts/<app-name>/`, one folder per application. See
+[how it works](docs/how-it-works.md) for the artifacts, ids and guarantees, or browse a
+**[complete example for a simple to-do app](examples/artifacts/)**: every phase 1 and
+phase 2 artifact, an OpenAPI contract and two ADRs, all approved and ready for
+implementation.
+
+## What's inside
+
+| | |
+| --- | --- |
+| **18 agents** | 3 orchestrators and 15 specialists across the three phases. [Catalog](docs/agents.md). |
+| **10 prompts** | Slash commands to start, resume, review and change each phase. [List](docs/agents.md#prompts). |
+| **2 platforms, 1 source** | Everything is written once in `aegis/` and generated for GitHub Copilot (`.github/`) and Claude Code (`.claude/`). |
+| **4 skills** | Artifact, ADR and implementation management, and Enterprise Standards grounding. |
+| **2 hooks** | A guard before implementation tool calls, and validation after every edit, on both platforms. |
+| **`artifact_tools` CLI** | Scaffold, validate, ADRs, contracts, diagrams and implementation state. [Reference](docs/cli-reference.md). |
+| **Reference MCP server** | Serves your standards from Markdown files. [Setup](docs/enterprise-standards-setup.md). |
+
+## Enterprise Standards
+
+Connect your organization's standards, policies, patterns and enterprise decisions through
+a read-only MCP server named `enterprise-standards-server`. You can run the included
+[reference server](examples/enterprise-standards-server/) on a folder of Markdown files, put
+your own server in front of an existing system, or run without one. The
+[setup guide](docs/enterprise-standards-setup.md) covers each option.
+
+## Security
+
+The implementation guard is a safeguard, not a sandbox. Review what agents change before
+you merge it, and treat standards content as untrusted input. Report vulnerabilities
+privately. See [SECURITY.md](SECURITY.md).
+
+## Contributing
+
+Contributions are welcome. See [CONTRIBUTING.md](CONTRIBUTING.md) for the setup, the
+checks CI runs and a checklist for each kind of component. This project follows the
+[Code of Conduct](CODE_OF_CONDUCT.md). Changes are recorded in the [changelog](CHANGELOG.md).
+
+## License
+
+[MIT](LICENSE)

aegis_sdlc-0.1.1/aegis/skills/artifact-management/assets/templates/adr.template.md

@@ -0,0 +1,53 @@
+---
+id: {{ADR_ID}}
+title: "{{TITLE}}"
+status: {{STATUS}}
+date: "{{DATE}}"
+component: "{{COMPONENT}}"
+supersedes: "{{SUPERSEDES}}"
+superseded_by: "{{SUPERSEDED_BY}}"
+deciders: "{{DECIDERS}}"
+---
+
+# {{ADR_ID}}: {{TITLE}}
+
+- **Status:** {{STATUS}}
+- **Date:** {{DATE}}
+- **Component/Domain:** {{COMPONENT}}
+- **Deciders:** {{DECIDERS}}
+- **Supersedes:** {{SUPERSEDES}}
+- **Superseded by:** {{SUPERSEDED_BY}}
+
+## Context
+
+_What is the issue that motivates this decision? Reference the driving requirements
+(`FR-*`, `NFR-*`) or components (`BP-*`) so the decision stays traceable._
+
+## Decision Drivers
+
+- _..._
+- _..._
+
+## Considered Alternatives
+
+1. **_Option A_** — _pros / cons._
+2. **_Option B_** — _pros / cons._
+3. **_Option C_** — _pros / cons._
+
+## Decision
+
+_The choice we are making, stated plainly._
+
+## Consequences
+
+### Positive
+
+- _..._
+
+### Negative / Trade-offs
+
+- _..._
+
+## Links
+
+- _Related ADRs, requirements, or external references._

aegis_sdlc-0.1.1/aegis/skills/artifact-management/assets/templates/architecture-decisions-index.template.md

@@ -0,0 +1,24 @@
+# Architecture Decision Records (ADRs)
+
+This index tracks every critical architectural decision for the platform. It is the
+semantic-routing entry point: filter by **Status** to avoid stale decisions and by
+**Component** to narrow a search before opening a record.
+
+- **Status** values: `proposed`, `accepted`, `rejected`, `deprecated`, `superseded`.
+- A `superseded` row must name its replacement in the **Consequences** column and set
+  `superseded_by` in its own frontmatter.
+- Records are immutable except for status transitions and back-links. Never renumber.
+
+| ID | Title | Date | Status | Component | Consequences | File |
+|------|-------|------|--------|-----------|--------------|------|
+| ADR-0001 | Record architecture decisions | {{DATE}} | accepted | Governance | Establishes the Nygard/MADR template for all future decisions. | [0001-adr-template.md](0001-adr-template.md) |
+
+## How to add a decision
+
+```bash
+python -m artifact_tools adr new "Event-driven topology" --status accepted --component "Core Topology"
+# Supersede an earlier decision:
+python -m artifact_tools adr new "Migrate catalogue to PostgreSQL" --supersedes ADR-0003
+```
+
+The tool auto-numbers the record, fills the template, and appends the row above.

aegis_sdlc-0.1.1/aegis/skills/artifact-management/assets/templates/data-architecture.template.md

@@ -0,0 +1,61 @@
+---
+artifact: data-architecture
+title: "{{TITLE}}"
+version: "0.1"
+status: draft
+last_updated: "{{DATE}}"
+phase: 2
+owner: artifact-manager
+---
+
+# Data Architecture — {{PROJECT_NAME}}
+
+> How data is structured, owned and governed. Entities use the `DM-` prefix and
+> `implements` the functional requirements (`FR-*`) whose data they hold. Proposed by
+> `data-architect`, written by `artifact-manager`.
+
+## Legend
+
+- **Store**: `relational` | `document` | `key-value` | `object` | `cache` | `search`
+- **Classification**: `public` | `internal` | `confidential` | `pii` | `pci`
+- **Status**: `draft` | `in-review` | `approved` | `removed`
+
+## 1. Logical Data Model (ERD)
+
+```mermaid
+erDiagram
+    ENTITY_A ||--o{ ENTITY_B : has
+    ENTITY_A {
+        uuid id PK
+        string name
+    }
+    ENTITY_B {
+        uuid id PK
+        uuid entity_a_id FK
+    }
+```
+
+## 2. Entities
+
+| ID | Entity | Store | Classification | implements | Status |
+|------|--------|-------|----------------|------------|--------|
+| DM-001 | _..._ | relational | internal | FR-001 | draft |
+
+## 3. Physical Design Notes
+
+_Primary keys, indexing strategy, partitioning/sharding, and referential integrity._
+
+## 4. Data Retention & Purging
+
+| Data domain | Retention period | Purge mechanism | Driver (NFR/regulation) |
+|-------------|------------------|-----------------|-------------------------|
+| _..._ | _..._ | _..._ | NFR-001 |
+
+## 5. Data Sovereignty & Residency
+
+_Where data must physically reside (e.g. Canada-only regions) and why._
+
+## Changelog
+
+<!-- artifact_tools changelog appends here -->
+- {{DATE}} — v0.1 — Initial scaffold (phase 2).

aegis_sdlc-0.1.1/aegis/skills/artifact-management/assets/templates/deployment-topology.template.md

@@ -0,0 +1,77 @@
+---
+artifact: deployment-topology
+title: "{{TITLE}}"
+version: "0.1"
+status: draft
+last_updated: "{{DATE}}"
+phase: 2
+owner: artifact-manager
+---
+
+# Deployment Topology — {{PROJECT_NAME}}
+
+> How the software runs in the cloud: networks, environments, and recovery. Nodes use
+> the `DEP-` prefix and `mitigates` the operational non-functional requirements
+> (`NFR-*`) they address. Proposed by `platform-architect`, written by
+> `artifact-manager`.
+
+## Legend
+
+- **Zone**: `public` | `private` | `data` | `management`
+- **Status**: `draft` | `in-review` | `approved` | `removed`
+
+## 1. Network Topology
+
+```mermaid
+flowchart TB
+    Internet((Internet)) --> LB[Load Balancer]
+    LB --> GW[API Gateway]
+    subgraph VPC
+        subgraph Public Subnet
+            GW
+        end
+        subgraph Private Subnet
+            APP[App Services]
+        end
+        subgraph Data Subnet
+            DB[(Database)]
+        end
+    end
+    GW --> APP --> DB
+```
+
+## 2. Topology Nodes
+
+| ID | Node | Zone | Runtime | mitigates | Status |
+|------|------|------|---------|-----------|--------|
+| DEP-001 | _..._ | private | container | NFR-001 | draft |
+
+## 3. Environments
+
+| Environment | Purpose | Scale | Promotion gate |
+|-------------|---------|-------|----------------|
+| Dev | _..._ | minimal | PR merge |
+| QA | _..._ | minimal | tests pass |
+| Staging | _..._ | prod-like | sign-off |
+| Prod | _..._ | full | change approval |
+
+## 4. CI/CD & Infrastructure as Code
+
+- **Pipeline**: _build → test → scan → deploy stages._
+- **IaC**: _Terraform / Ansible — module layout and state management._
+- **Promotion**: _how artifacts move Dev → QA → Staging → Prod._
+
+## 5. Disaster Recovery
+
+| Metric | Target | Implementation |
+|--------|--------|----------------|
+| RTO | _..._ | _..._ |
+| RPO | _..._ | _..._ |
+
+_Backups, replication, failover region, and restore drills. Targets derive from
+`NFR-*` reliability requirements._
+
+## Changelog
+
+<!-- artifact_tools changelog appends here -->
+- {{DATE}} — v0.1 — Initial scaffold (phase 2).

aegis_sdlc-0.1.1/aegis/skills/artifact-management/assets/templates/executive-briefing.template.md

@@ -0,0 +1,45 @@
+---
+artifact: executive-briefing
+title: "{{TITLE}}"
+version: "0.1"
+status: draft
+last_updated: "{{DATE}}"
+phase: 1
+owner: artifact-manager
+---
+
+# Executive Briefing — {{PROJECT_NAME}}
+
+> One page for stakeholders. Synthesized from the other five artifacts. Keep it tight.
+
+## The Ask
+_One sentence: what decision or support is needed._
+
+## Opportunity
+_The problem and the value of solving it — 2-3 sentences._
+
+## Proposed Solution
+_What we will build, at a glance._
+
+## Scope Snapshot
+- **In:** _..._
+- **Out (now):** _..._
+
+## Success Metrics
+| Metric | Target |
+|--------|--------|
+| _..._ | _..._ |
+
+## Key Risks
+| ID | Risk | Likelihood | Impact | Mitigation |
+|------|------|-----------|--------|-----------|
+| RISK-001 | _..._ | med | high | _..._ |
+
+## Status
+- **Phase:** 1
+- **Overall readiness:** draft
+
+## Changelog
+
+<!-- artifact_tools changelog appends here -->
+- {{DATE}} — v0.1 — Initial scaffold (phase 1).

aegis_sdlc-0.1.1/aegis/skills/artifact-management/assets/templates/functional-requirements.template.md

@@ -0,0 +1,36 @@
+---
+artifact: functional-requirements
+title: "{{TITLE}}"
+version: "0.1"
+status: draft
+last_updated: "{{DATE}}"
+phase: 1
+owner: artifact-manager
+---
+
+# Functional Requirements — {{PROJECT_NAME}}
+
+> What the system must do. Each requirement is atomic, testable, and traces back to
+> a product goal (`PR-*`) or a user journey (`UJ-*`). IDs use the `FR-` prefix.
+
+## Legend
+
+- **Priority**: `must` | `should` | `could` | `wont`
+- **Status**: `draft` | `in-review` | `approved` | `removed`
+- **traces_to**: comma-separated `PR-*` / `UJ-*` ids that justify this requirement.
+
+## Requirements
+
+| ID | Requirement | Priority | traces_to | Status |
+|------|-------------|----------|-----------|--------|
+| FR-001 | The system shall _..._ | must | PR-001 | draft |
+
+## Acceptance Criteria
+
+### FR-001
+- Given _..._, when _..._, then _..._.
+
+## Changelog
+
+<!-- artifact_tools changelog appends here -->
+- {{DATE}} — v0.1 — Initial scaffold (phase 1).