What problem does it solve? Before planning UI work, developers waste time re-discovering repo conventions, in-flight branch changes, and tooling rules that will block implementation. This Skill collects those fixed facts once into a single bounded artifact that downstream planning, implementation, and review skills can consume. ## Core Features & Use Cases - Fact gathering without planning: Collects repo learnings, git branch state, TypeScript/ESLint/Prettier constraints, and user-named files while deliberately leaving affected-file discovery to the planning stage. - Handoff and decision seeding: Reuses prior savepoint handoffs and resolved decision memos so settled questions are not re-litigated. - Bounded artifact output: Writes a distilled analysis file (target under 150 lines) with a fixed frontmatter schema, symlinked as analysis-latest.md for /plan-ui, /impl-ui, /validate-ui, and /pr-review-ui. - Use Case: Before asking for a plan to add a new settings form, run this Skill to capture which files the task names, what in-flight branch edits might conflict, and which lint rules will reject common patterns. ## Quick Start Ask the assistant to analyze this task and gather the constraints for adding a new settings form before any planning begins.
