recipe-plugin-compliance
Recipe: Plugin Compliance Sweep
Recipe skill for sweeping all marketplace bundles against plugin architecture standards. Loaded by phase-3-outline when this recipe is selected.
Input Parameters
| Parameter | Source |
|---|---|
plan_id |
From phase-3-outline |
The recipe's discovery metadata (recipe_domain, recipe_profile, recipe_package_source) is declared in this skill's YAML frontmatter — manage-config list-recipes reads it from frontmatter, the sole source of truth; the markdown body is never scanned for these keys.
Workflow
Step 0: Gather + expand + persist the coverage cell
This recipe implements the coverage-gathering contract. At invocation, gather the (thoroughness, scope) cell from the user via the contract's canonical AskUserQuestion shape — a scope question (change-set/artifact/component/module/overall + an explicit inherit (default — behave exactly as today)) and a thoroughness question (T1…T5 + inherit). The coupling constraint (reject thoroughness ≥ T4 ∧ scope < component) constrains the offered scope options when the user picks T4/T5.
Validate + expand the gathered pair in one call: manage-config coverage expand --thoroughness {T} --scope {S} validates the literal pair (re-prompt on coverage_coupling_violation; do NOT re-implement the coupling math) AND returns the operational instruction block. Then persist BOTH the identifier and the expanded instruction to status.json metadata (this recipe is plan-bound):