القائمة
Implementation gap analysis. Verify what has to be implemented. Verify what was implemented. Compare plan to current state.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Perform code review. Quality analysis. Acceptance criteria verification. Best practices review.
Transform extracted epics and user stories into Jira-ready format following a benchmark template. Handles field mapping, formatting for Jira markdown compatibility, two-gate user review, and guidance for Jira issue creation via Atlassian tools.
Identify and structure epics and user stories from workshop materials (cleaned transcripts, Figma designs, codebase analysis, and other documents). Produces a business-oriented task breakdown with dependencies, assumptions, and open questions.
Analyze extracted epics and user stories for quality gaps, missing edge cases, and improvement opportunities. Runs domain-agnostic analysis passes, optionally enriches findings with Jira board context, and produces accept/reject suggestions that refine the task list before Jira formatting.
Design the architecture to solve a given task. Propose the solutions to be used to deliver the task following the best practices and standards.
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.
| name | tsh-implementation-gap-analysing |
| description | Implementation gap analysis. Verify what has to be implemented. Verify what was implemented. Compare plan to current state. |
| user-invocable | false |
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.