intended-vs-implemented

SKILLWorkflowCommunity
v0.0.0phurynMITAktualisiert vor 1 Mon.Quelle →

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 →
25kRepo-Sterne
1Clients
1Formate
vor 1 Mon.Letzte Aktualisierung
Skill
Autorphuryn
Version0.0.0
LizenzMIT
KategorieWorkflow
Formateskill.md
PromptÖffnen (siehe Tab „Prompt“)
Kompatibilität
Claude✓ Unterstützt
Cursor
Copilot
ChatGPT
Gemini
Über

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

Schlagwörter
skillclaude