tp-design-complete

Design Complete

Mark a finished design as complete, archive it out of the active designs directory, and clean up session state.

Argument: {design-name} (required) — must match an existing directory under three-pillars-docs/tp-designs/.

Steps

1. Run first-run preflight per skills/_shared/first-run.md.

0a. Run cwd preflight per skills/_shared/cwd-preflight.md: python3 "$TP_ROOT"/skills/_shared/cwd_preflight.py {design-name}. Exit 3 → stop and show the cd fix. Exit 0 → continue.

1. Validate the design name per skills/_shared/validate-name.md.
2. Resolve the design directory: three-pillars-docs/tp-designs/{design-name}/. If it doesn't exist, tell the user and stop.
3. Check if -learn has been run (hard-blocks unless --skip-learn was passed): Determine whether this is a spike (has spike-results.md) or a full design (has implementation-audit.md).
   • For spikes: Check if the product_roadmap.md Design Inventory table has been updated with the spike's verdict (GO/PARTIAL/NO-GO). If not, refuse to proceed:

     Refusing to complete: /tp-spike-learn hasn't been run yet — the Design Inventory doesn't carry a GO/PARTIAL/NO-GO verdict. That step propagates findings into project docs and scans for affected downstream designs; skipping it leaves the roadmap silently stale. Run /tp-spike-learn {design-name} first, then re-invoke this skill. If you have a specific reason to skip (e.g., the spike was a one-off scratchpad with no roadmap presence), re-invoke with --skip-learn.

   • For full designs: Check if the product_roadmap.md Design Inventory status reflects completion. If it still says "Designed" or "Pending", refuse to proceed:

     Refusing to complete: /tp-design-learn hasn't been run yet — the Design Inventory status is still "Designed" / "Pending" / "Implementing". That step propagates implementation results into product_roadmap.md, architecture.md, and known_issues.md, updates the Design Inventory status, and scans for affected sibling designs. Skipping it causes the roadmap to drift silently across the completion boundary. Run /tp-design-learn {design-name} first, then re-invoke this skill. If you have a specific reason to skip — legacy designs that pre-date this rule, or designs where learn was run out-of-band and the roadmap status is intentionally stale — re-invoke with --skip-learn.

   • --skip-learn escape hatch: If the user passed --skip-learn, log a one-line notice (Proceeding without learn per --skip-learn flag) and continue. The flag exists for legacy designs and well-understood out-of-band cases; it must not become the default workflow. Do not silently treat absence-of-flag as override.
4. Show a summary of what will happen:
   • The completion date that will be stamped (today's date, YYYY-MM-DD)
   • Whether handoff.md exists and will be archived (banner added)
   • The destination: three-pillars-docs/completed-tp-designs/{design-name}/
   • The current branch and the base branch — after archival, a commit will be made on the current branch and (if the current branch is not the base) a PR back to base will be offered
5. Ask for confirmation before proceeding. A simple "Complete this design?" is enough.
6. On confirmation, execute these steps in order: