intended-vs-implemented

SKILLWorkflowcommunauté
v0.0.0phurynMITMis à jour il y a 1 moisSource →

The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to

Community-submitted skill. Not yet reviewed by the Forge team. Full prompt content may not be available.Request review →
25kÉtoiles du dépôt
1Clients
1Formats
il y a 1 moisDernière mise à jour
Skill
Auteurphuryn
Version0.0.0
LicenceMIT
CatégorieWorkflow
Formatsskill.md
PromptOuvrir (voir l’onglet Prompt)
Compatibilité
Claude✓ Pris en charge
Cursor
Copilot
ChatGPT
Gemini
À propos

The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against document

Mots-clés
skillclaude