What problem does it solve? Infrastructure considerations that fall outside the PRD and the contract often get lost or rewritten inconsistently across features. This Skill maintains a single project-level infra-notes.md file that captures deploy units, secrets, persistence, packaging, and CI/CD concerns, and ensures every listed need maps to real work. ## Core Features & Use Cases - Profile-driven templates: Selects between a cross-side/cloud template (deploy units, secrets & identity, CI/CD) and a single-side/desktop template (local DB, backup/restore, packaging, updates) based on the declared profile. - Amend-never-redraft discipline: Drafts the file once during explore, then emits deltas on later features so prior packaging, backup, and update decisions are preserved. - Downstream traceability: Every infra need must map to an infra task/block, an enforced_by ADR, or a CI gate, preventing zombie documentation. - Use Case: While modeling a desktop app feature, invoke this Skill to record the local database migration strategy and per-OS packaging needs, each linked to a concrete task or ADR. ## 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.
