write-infra-notes

Writes and amends project-level infrastructure notes mapping infra needs to tasks, ADRs, and CI gates.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/lucolucus/mismagent --skill write-infra-notes-lucolucus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-infra-notes
Source: https://github.com/lucolucus/mismagent/tree/main/plugins/mismagent/skills/write-infra-notes
Command: npx skills add https://github.com/lucolucus/mismagent --skill write-infra-notes-lucolucus

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about write-infra-notes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document infrastructure requirements for a software project?

Create a project-level infra-notes.md that lists environments, secrets, persistence, packaging, and CI/CD needs, then map each need to a concrete task, ADR, or CI gate. This Skill generates that file using a template matched to your deployment profile.

What is the difference between the cloud and desktop infra templates?

The cloud/cross-side template covers independent deploy units, secrets and identity, observability, and CI/CD pipelines. The desktop/single-side template covers the desktop stack, local DB migrations, backup/restore, per-OS packaging, and app updates.

Should infra notes be rewritten for each new feature?

No. The file is drafted once per project and amended with a delta on later features, leaving prior decisions untouched. Only the architect amends it during consolidation; explore drafts it only when it does not exist.

When should an infrastructure constraint become an ADR?

Mechanical constraints such as Managed Identity instead of connection strings or forward-only migrations should be flagged as enforced_by ADR candidates. The write-adr skill then formalizes them into grep-rules the verifier checks.

What happens to infra needs that produce no tasks or gates?

They are not written. The survival test requires every listed need to map to an infra task, an enforced_by ADR, or a CI gate; anything else is considered noise and excluded from the file.