Pre-launch readiness checklist generated from SDL and deployment configuration
From architectnpx claudepluginhub navraj007in/architecture-cowork-plugin --plugin architect/launch-checklistGenerates a tailored launch checklist for a feature or product release, covering engineering, infrastructure, documentation, communication, and rollback readiness with owners and completion tracking.
/launch-checklistGenerates a comprehensive pre-launch checklist using the deliver-launch-checklist skill and TEMPLATE.md format, based on user context arguments.
/architect:launch-checklist — run after blueprint and scaffold are complete, before go-live.
Generate a comprehensive pre-launch readiness checklist tailored to the project's architecture, deployment strategy, and compliance requirements. Ensures nothing is missed before the product goes live. Useful for founders, development agencies handing off to clients, and DevOps teams.
Read in this order:
architecture-output/_state.json — read first if it exists; provides compact project (name, stage), tech_stack (auth provider, deployment, integrations), and components (list with types) — use these instead of reading full markdown files for basic project facts_state.json is absent or lacks tech_stack/components. Check solution.sdl.yaml first; if absent, read sdl/README.md then the relevant module files.architecture-output/executive-summary.md if it exists for high-level context (typically small)docker-compose.yml, .github/workflows/, Dockerfile, fly.toml, vercel.json, netlify.toml, render.yaml.env.example for required secrets and configarchitecture-output/security-scan.md if it existsLoad:
Organize the checklist by category. For each item, include:
[ ] checkbox (unchecked)[Required], [Recommended], or [Optional]Categories:
auth section → skip authentication-related itemsdeployment section → mark all infrastructure items as [Required] with note "deployment not yet configured"observability section → mark monitoring items that are already configured as [Configured] instead of checkboxmvp → mark legal/compliance items as [Recommended] not [Required]product → mark all legal/compliance items as [Required]Write the checklist to architecture-output/launch-checklist.md.
Format as a single markdown document with clear category headings (## level) and checkbox items.
Include a summary at the top:
# Launch Checklist — [Project Name]
Generated: [date]
**Summary**: X required items, Y recommended, Z optional
**Launch readiness**: [Ready / Needs attention / Not ready]
Silently probe both Confluence and Notion to check which (if any) is connected.
Check Confluence — attempt search_content with a lightweight query (e.g. query: "test", limit: 1):
artifact: "launch-checklist", projectName, spaceKey, parentPageId, projectDirCheck Notion — attempt notion_search with query: "", page_size: 1:
artifact: "launch-checklist", projectName, parentPageId or databaseId, projectDirIf neither is connected, skip silently.
After writing architecture-output/launch-checklist.md, append one line to architecture-output/_activity.jsonl:
{"ts":"<ISO-8601>","phase":"launch-checklist","outcome":"completed","files":["architecture-output/launch-checklist.md"],"summary":"Generated pre-launch checklist with <N> required, <Y> recommended, and <Z> optional items."}
Replace <N>, <Y>, <Z> with actual item counts. Rules: append only — never overwrite. Single JSON object per line, no pretty-printing.
After writing all output files, merge a completion marker into architecture-output/_state.json:
_state.json (or start with {})launch_checklist field shown below — do NOT overwrite other fieldsarchitecture-output/_state.json{
"launch_checklist": { "generated_at": "<ISO-8601>", "item_count": <N> }
}
(Replace <N> with the total number of checklist items generated.)
Emit the completion marker:
[LAUNCH_CHECKLIST_DONE]
This ensures the launch-checklist phase is marked as complete in the project state.
/architect:launch-check — it scores the project against a checklist in seconds by scanning the file system directly