What problem does it solve? Infrastructure considerations that fall outside the PRD and the contract often get lost or rewritten inconsistently per feature, silently dropping decisions about packaging, backup, secrets, and CI/CD. This Skill maintains a single project-level infra-notes.md file that is drafted once and amended across features, never redrafted. ## Core Features & Use Cases - Profile-driven templates: Selects between a cloud/cross-side template (deploy units, secrets & identity, CI/CD) and a desktop/single-side template (local DB migrations, backup/restore, per-OS packaging, updates) based on the declared sides. - Amend-not-redraft discipline: Reads the existing file on later features and emits only a delta, preserving decisions consolidated by the architect. - Survival test enforcement: Every listed infra need must map to an infra task, an enforced_by ADR, or a CI gate, otherwise it is excluded as noise. - Use Case: While modeling a new feature for a desktop app, invoke this Skill to add the new backup requirement to the existing infra-notes.md without touching the packaging and migration decisions recorded earlier. ## Quick Start Ask the agent to draft or amend the project's infra-notes.md for the current feature using the template matching the declared profile sides.