.github/skills/tsh-implementation-gap-analysing/SKILL.md
Implementation gap analysis. Verify what has to be implemented. Verify what was implemented. Compare plan to current state.
npx skillsauth add thesoftwarehouse/copilot-collections tsh-implementation-gap-analysingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill helps compare the current state of the system to expected changes. It validates what has to be implemented, what was already implemented and what has to be modified in order to deliver the feature.
Use the checklist below and track your progress:
Analysis progress:
- [ ] Step 1: Analyse all available information about the task
- [ ] Step 2: Analyse the current system state
- [ ] Step 3: Compare the expected result to the current system
- [ ] Step 4: Prepare the report
Step 1: Analyse all available information about the task
Check the conversation history and .research.md files to fully understand the goal of the task. Make sure to deeply understand what we want to implement.
Step 2: Analyse the current system state
Go through the current codebase and look for items that are related to the current task.
Step 3: Compare the expected result to the current system
Based on the current code and task information, verify which part have to be created from scratch, which have to be modified and which can be re-used as they are.
Step 4: Prepare the report
Prepare a analysis report following the ./implementation-gap-analysis.example.md template.
Don't add or remove any sections from the template. Follow the structure and naming conventions strictly to ensure clarity and consistency.
development
Custom hook and composable patterns — naming, composition, stable return shapes, lifecycle cleanup, and testing strategies. Use when writing reusable logic units (React hooks, Vue composables), refactoring logic into hooks, debugging hook behavior, or reviewing hook implementations.
testing
UI verification criteria, structure checklists, severity definitions, and tolerance rules for comparing implementations against Figma designs. Use for verifying UI matches design, understanding what to check, and determining acceptable differences.
development
Clean raw workshop or meeting transcripts from small talk, filler words, and off-topic tangents. Extract and structure business-relevant content into a standardized format with discussion topics, key decisions, action items, and open questions.
development
Discover and establish technical context before implementing any feature. Prioritize project instructions, existing codebase patterns, and external documentation in that order. Use for any task requiring understanding of project conventions, coding standards, architecture patterns, and established practices before writing code.