← ClaudeAtlas

session-post-implementationlisted

Post-implementation refinement workflow. Use after completing a major feature or plan implementation to simplify, review, and document the code. Triggers on "/session-post-implementation" or when user says "run the iteration workflow" or "polish this implementation".
matshoppenbrouwers/session-flow · ★ 3 · AI & Automation · score 76
Install: claude install-skill matshoppenbrouwers/session-flow
# Post-Implementation Refinement Execute this sequential workflow after completing a major feature or plan implementation. Open with one sentence saying what you are about to do and what it will produce. ## Workflow Configuration Before starting, use **AskUserQuestion** to let the user configure the workflow. Present both questions together at the start (not between steps). **Question 1: Pipeline scope** Use AskUserQuestion: - question: "How thorough should post-implementation be?" - header: "Scope" - multiSelect: false - options: - A) label: "Full pipeline (Recommended)", description: "All steps: simplify, review, security & liability audit, test suite, architecture docs, and manual test plan. Best after completing a major feature." - B) label: "Standard", description: "Simplify, review, test suite, and commit. Skips security audit, architecture docs, and manual test plan." - C) label: "Quick", description: "Simplify, review, and commit only. Fastest option for minor changes." **Recommend by consequence, not size.** Read the work item's accepted scope first, then name one recommended preset and the reason for it in the same message as the question. A change is consequential when it touches authority or credentials, writes data the user cannot recreate, has an external effect, or changes a contract another repository reads — recommend Full, however few lines it changed. A change whose cause is understood, that nothing depends on, and that an existing check alread