From structured-english
Review a markdown specification for ambiguity, contradiction, and inferred intent
npx claudepluginhub reggiechan74/cc-plugins --plugin structured-english<path to markdown spec file># Assess Inferred Intent Analyze a markdown specification file (slash command, SKILL.md, agent.md, or any structured spec) for areas of ambiguity, contradiction, or inferred intent. Present findings to the user for resolution, then apply the clarifications to the document. ## Workflow ### Step 1: Read the Document If the user provided a file path in the arguments, read it. Otherwise, ask the user: - "Which markdown specification file should I review?" Read the full file content before proceeding. ### Step 2: Analyze for Issues Examine the document for three categories of problems: ...
Analyze a markdown specification file (slash command, SKILL.md, agent.md, or any structured spec) for areas of ambiguity, contradiction, or inferred intent. Present findings to the user for resolution, then apply the clarifications to the document.
If the user provided a file path in the arguments, read it. Otherwise, ask the user:
Read the full file content before proceeding.
Examine the document for three categories of problems:
Ambiguity — language or structure that could be interpreted multiple ways:
Contradiction — statements that conflict with each other:
Inferred Intent — behavior that is implied but never stated:
For each issue found, prepare a structured finding with:
If no issues are found, tell the user the spec looks clear and stop.
Use AskUserQuestion to walk through the findings. Group related issues into a reasonable number of questions (aim for 1-4 questions per round to stay within tool limits). For each issue:
Continue presenting rounds of questions until all issues are resolved.
After all issues are resolved, revise the document to incorporate the user's decisions. Changes should:
After applying clarifications, use AskUserQuestion to ask:
sesf skill rules.hsf skill rules.If the user selects SESF or HSF, load the corresponding skill (${CLAUDE_PLUGIN_ROOT}/skills/sesf/SKILL.md or ${CLAUDE_PLUGIN_ROOT}/skills/hsf/SKILL.md) and rewrite the clarified document to conform to that format's rules. Preserve all domain logic — only change the format.
Use AskUserQuestion to ask the user how to save:
<original-name>-clarified.md alongside the original