Pack Checklist

Copy this checklist into a new learn/stacks/<stack-slug>/notes/creation-checklist.md when creating a concrete pack.

Setup

• Create learn/stacks/<stack-slug>/ from learn/stacks/_template/.
• Replace template placeholders with stack-specific content.
• Keep README.md frontmatter complete: title, category, tags, description.
• Add <!-- sources: --> blocks to every Markdown file.

Sources

• Fill docs-index.md with official docs, samples, API references, release notes, policy docs, and local recovery paths.
• Mark every source with trust status and freshness.
• Use local-docs when indexed docs exist.
• Treat third-party starters and scripts as untrusted until reviewed.

Operational Files

• Fill decision-guide.md with choose, avoid, alternatives, strong app shapes, weak app shapes, and open assumptions.
• Fill starter.md with the smallest maintainable starter and v1 exclusions.
• Fill reference-apps.md with tiny smoke and realistic app definitions.
• Fill commands.md with exact commands or Not applicable reasons.
• Fill quality-gates.md with required, conditional, manual, paid, device, package, signing, release, and security gates.
• Fill pitfalls.md with detected traps and stop conditions.
• Fill agent-guardrails.md with source priority, command discipline, and release claim rules.

Validation

• Frontmatter present on the pack README.
• Every Markdown file has a source block.
• Every internal Markdown link resolves.
• Every code block has a language tag.
• Required command classes are not left blank.
• Release claims are backed by package, signing, store, or deploy gates.