What problem does it solve? Technical refinement of user stories often misses hidden metadata dependencies, causing broken deployments and untracked impact. This Skill runs impact analysis against a Salesforce metadata dependency graph, enforces naming conventions, breaks stories into technical tasks, and persists everything to a repo-resident backlog. ## Core Features & Use Cases - Metadata Impact Analysis: Detects the sf-graphify plugin or falls back to the built-in sf-metadata-index to query transitive dependencies and dependents for every component a story touches. - NAMING Convention Enforcement: Applies PascalCase API naming with mandatory descriptions and checks for collisions against existing metadata entries. - Local Backlog Persistence: Stores refined stories and technical tasks in the repo-resident .setup-agents/state/tasks.jsonl via sf setup-agents task create, keeping git as the source of truth. - Use Case: A Technical Architect refining a story that adds a field to the Account object uses this Skill to identify all dependent Apex classes and flows, generate technical tasks covering sharing and async implications, and record the refined story in the local backlog for QA regression targeting. ## Quick Start Ask the agent to technically refine a specific user story by running metadata impact analysis and saving the resulting technical tasks to the local backlog.
