cuioss/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 | | recipe_domain | plan-marshall-plugin-dev | | recipe_profile | implementation | | recipe_package_source | packages |

Workflow

Step 1: Resolve Skills

python3 .plan/execute-script.py plan-marshall:manage-config:manage-config \
  resolve-domain-skills --domain plan-marshall-plugin-dev --profile implementation

Collect core + implementation defaults and optionals for skill references in deliverables.

Step 2: List Modules

python3 .plan/execute-script.py plan-marshall:manage-config:manage-config \
  skill-domains get --domain plan-marshall-plugin-dev

Then list available modules (marketplace bundles):

python3 .plan/execute-script.py plan-marshall:manage-architecture:architecture modules

Present module list to user for filtering. User may select all or a subset.

Step 3: Create Deliverables Per Bundle

For each selected module (bundle), load its packages:

python3 .plan/execute-script.py plan-marshall:manage-architecture:architecture \
  module --name {module_name} --full

Iterate the packages field. For each package (skill/agent/command directory), create one deliverable:

Title: Compliance: {module}/{package}
change_type: tech_debt
execution_mode: automated
domain: plan-marshall-plugin-dev
module: {module_name}
profile: implementation
skills: {resolved from Step 1}
affected_files: {files from architecture data}

Focus areas per deliverable:

• SKILL.md/agent/command frontmatter correctness
• Enforcement block presence and structure (script-bearing skills)
• Standards document cross-references
• Script naming and output contract compliance

Step 4: Write Solution Outline

4a. Read the deliverable template to understand the required structure:

Read: marketplace/bundles/plan-marshall/skills/manage-solution-outline/templates/deliverable-template.md

4b. Read an example to see the full document skeleton:

Read: marketplace/bundles/plan-marshall/skills/manage-solution-outline/examples/refactoring.md

4c. Resolve the target path:

python3 .plan/execute-script.py plan-marshall:manage-solution-outline:manage-solution-outline \
  resolve-path --plan-id {plan_id}

4d. Write the solution outline using the Write tool to {resolved_path}. The document MUST include these sections in order:

• # Solution: {title} header with plan_id, created, compatibility metadata
• ## Summary — 2-3 sentences describing approach
• ## Overview — ASCII diagram showing scope
• ## Deliverables — All deliverables from Step 3, grouped by module, using the template structure

4e. Validate the written outline:

python3 .plan/execute-script.py plan-marshall:manage-solution-outline:manage-solution-outline \
  write --plan-id {plan_id}