skills.rest
editor-code-assistant
editor-code-assistantOFFICIAL
Explore all skills by this author →
WebsiteGitHub

weed

Identify divergences between Allium specifications and implementation code.

5|4|Updated Mar 10, 2026
Search Tags:#implementation#verification#code-review#spec-audit#divergence#allium#weed
One-click install
npx skills add https://github.com/editor-code-assistant/eca-plugins --skill weed-editor-code-assistant
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: weed
Source: https://github.com/editor-code-assistant/eca-plugins/tree/main/plugins/allium/skills/weed
Command: npx skills add https://github.com/editor-code-assistant/eca-plugins --skill weed-editor-code-assistant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weed the Allium garden by identifying where specifications and implementation diverge, enabling timely resolution and alignment.

Core Features & Use Cases

  • Surface divergences between spec and code for all entities, rules, and transitions.
  • Provide actionable classifications (Spec bug, Code bug, Aspirational design, Intentional gap) and structured outputs.
  • Support iterative workflows (check, update-spec, update-code) with guidance for remediation.

Quick Start

Run a divergence check to surface mismatches between Allium specs and their implementations.

Frequently Asked Questions about weed

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify divergences between specifications and implementation code?▼

To identify spec-code divergences, you can audit alignment across entities, rules, and transitions. This process surfaces mismatches between your specifications and implementation code, producing structured findings that guide remediation workflows.

What is a spec-code audit and how does it work?▼

A spec-code audit checks alignment between specifications and implementation code. It identifies divergences across project entities, rules, and transitions, then classifies findings to enable iterative check, update-spec, or update-code workflows for maintaining traceability.

What classifications are used when reporting specification and code mismatches?▼

Specification and code mismatches are classified as Spec bug, Code bug, Aspirational design, or Intentional gap. These actionable classifications structure the findings to guide specific remediation workflows for each divergence type.

How do I run a divergence check for Allium project entities and transitions?▼

Run a divergence check by applying the audit to Allium project entities, rules, and transitions. This surfaces spec-code alignment mismatches and produces structured findings to support iterative update-spec or update-code remediation workflows.

Do I need specific dependencies to perform a spec-code alignment audit?▼

No specific dependencies are required to perform a spec-code alignment audit. The process operates directly on your specifications and implementation code to surface divergences and produce structured findings for remediation.

Related Skills

Explore More Software Engineering Skills→
juxtjuxt
10

tend

Edit and validate Allium behavioral specification files against CLI tooling.

Official
Advanced
rhussrhuss
107

evolve

Detect spec/code divergences and categorize mismatches for guided resolution.

Community
Basic
davidYichengWeidavidYichengWei
159

workflow-code-generation

Generate and execute code change tasks with spec verification.

Community
Advanced
jmbeachjmbeach

linked-intent-dev

Execute a six-phase software development workflow from HLD check to code implementation.

Community
Advanced