post-phase-reconciliation
Mandatory documentation sync after a phase ships
git clone --depth 1 https://github.com/debugbundle/debugbundle /tmp/post-phase-reconciliation && cp -r /tmp/post-phase-reconciliation/.agents/skills/post-phase-reconciliation ~/.claude/skills/post-phase-reconciliationSKILL.md
# Post-Phase Doc Reconciliation After all slices in a phase are green and committed, run this reconciliation before moving on. ## Steps 1. Diff all files changed in the phase. 2. Cross-reference against: - `/spec/*` - `/contracts/*` - `/rules/*` - `/SYSTEM_OVERVIEW.md` - `/ARCHITECTURE_MAP.md` 3. Update any doc that no longer matches implemented reality. 4. Update the local `/STATUS.md` tracker when present — move completed items with key details of what was done. 5. Verify `/rules/glossary.md` — any new terms introduced must be defined. ## Rules - This is not "update docs when you remember." It is a mandatory step at every phase boundary. - If architecture or module boundaries changed, `SYSTEM_OVERVIEW.md` and `ARCHITECTURE_MAP.md` must be updated.
Use DebugBundle MCP and CLI workflows to investigate runtime errors/failures, fetch bundles, manage operational debugging surfaces, run verification, and guide fixes when captured operational evidence is relevant.
Use this skill for any UI, UX, layout, interaction, component, accessibility, or design-system related task. It helps choose familiar patterns, preserve system consistency, and avoid low-quality generated UI.
Structured "what can still break" audit before marking a phase or slice complete
Ensure clean session continuity when context is getting long or session is ending
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".