intended-vs-implemented

SKILLFlujo de trabajocomunidad
v0.0.0phurynMITActualizado hace 1 mFuente →

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 →
25kEstrellas del repo
1Clientes
1Formatos
hace 1 mÚltima actualización
Skill
Autorphuryn
Versión0.0.0
LicenciaMIT
CategoríaFlujo de trabajo
Formatosskill.md
PromptAbrir (ver la pestaña Prompt)
Compatibilidad
Claude✓ Compatible
Cursor
Copilot
ChatGPT
Gemini
Acerca de

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

Palabras clave
skillclaude