workflowlisted

# Development Workflow A structured approach to software development that emphasizes understanding, minimal implementation, testing, documentation, and clean commits. --- ## Overview ``` Step 1: Focus Problem → Understand before coding Step 2: Prevent Overdev → Only build what's needed (YAGNI) Step 3: Test First → Red-Green-Refactor Step 4: Document → Keep it clear and current Step 5: Smart Commit → Conventional Commits ``` --- ## Step 1: Focus Problem (`/focus-problem`) **Goal:** Thoroughly understand the problem before writing code. ### Checklist - [ ] What is the user need? (Who / What / Why) - [ ] What defines success? (How to verify completion?) - [ ] What are the boundaries? (What NOT to do?) - [ ] What files/modules are affected? - [ ] Is there existing similar functionality? ### Use Explore Agent ```markdown Task(subagent_type="Explore", model="haiku", prompt=""" Explore the codebase for: [feature name] (thoroughness: medium) Find related files, similar implementations, and test patterns. """) ``` --- ## Step 2: Prevent Overdev **Goal:** Ensure minimal viable implementation (YAGNI principle). ### Red Flags ``` "We might need this later..." → Don't build it now "Just in case..." → YAGNI "Let's make it generic..." → Solve current problem only "We should create a framework..." → Write concrete implementation ``` ### Checklist - [ ] Is there immediate need for this? - [ ] Is this over-abstracted? - [ ] Can this be simpler? - [ ] Are we