Menu
Run mechanical `.idd/intent/` consistency checks without editing files.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Check whether implementation behavior matches durable product intent in `.idd/intent/`.
Implement behavior from current `.idd/intent/` product intent and verify the code against the relevant specification.
Update `.idd/intent/` product intent from confirmed implementation behavior.
Diagnose `.idd/intent/` product intent structure and recommend reorganizations without editing files.
Clarify real product intent before changing `.idd/intent/`, using focused customer-development questions and simplification options without editing product intent, planning implementation, or writing code.
Update current `.idd/intent/` product intent from a user-requested behavior change, preferring existing specs over new specs.
Based on SOC occupation classification
| name | idd-intent-lint |
| description | Run mechanical `.idd/intent/` consistency checks without editing files. |
Use this skill to perform cheap mechanical validation over .idd/intent.
Formula:
idd-intent-lint = cheap mechanical validation, not semantic review
Use it when the user asks whether .idd/intent is mechanically consistent.
Check that:
.idd/intent/README.md exists;.idd/intent/INDEX.md exists;INDEX.md exists;.idd/intent/ is listed in INDEX.md;.idd/intent has no archive directory;.idd/intent/import-report.md does not exist;.idd/intent;INDEX.md has no Archived section;.idd/intent references .idd/intent/archive/...;Related, Replaces, Supersedes, Depends on, and similar numeric
relation references point to existing current numbered docs;.worklog references except in
source/history sections;idd-intent-lint must fail if:
.idd/intent;.idd/intent/import-report.md exists;.idd/intent;INDEX.md contains an Archived section;INDEX.md links to deleted document storage;.idd/intent references .idd/intent/archive/...;Related, Replaces, Supersedes, Depends on, or similar
relation points to a missing current numbered doc;Status: Current, Status: Superseded,
Superseded by, or another explicit lifecycle status;INDEX.md models ordinary specs as Current, Completed, Superseded, or
another lifecycle status;dotnet build, dotnet test, npm test, mvn test,
gradle test, cargo test, or pytest;Warn, without failing automatically, when a normative spec contains source file
names such as .cs, .java, .ts, or .py; private-style identifiers;
method-call notation; constructor names; dependency-injection registration
instructions; test method names; CLI commands; or terms such as remaining,
finish, complete migration, or follow-up implementation. Public APIs and
durable architecture types may legitimately match these patterns.
Do not apply implementation-leakage checks to clearly non-normative sections
named Source history, Migration source, Provenance, Imported from, or
Historical note; those sections must not state current requirements.
Mechanical lint may flag suspicious wording. It must not claim to have completed semantic review.
# IDD Intent Lint Report
## Result
pass | fail
## Errors
Problems that should be fixed.
## Warnings
Suspicious structure or wording.
## Suggested fixes
Concrete file-level recommendations.
User request:
Check whether `.idd/intent` is mechanically consistent.
Expected behavior:
idd-intent-lint;INDEX.md, files, links, required sections, and stale .worklog
references;Do not use this skill to:
Use idd-intent-audit for broad structural diagnostics.