community-backlog-submit

Records general plugin capability gaps as sanitized YAML backlog items for community contribution.

26|8|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/vibeic/vibe-ic --skill community-backlog-submit-vibeic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: community-backlog-submit
Source: https://github.com/vibeic/vibe-ic/tree/main/vibe-ic-marketplace/plugins/vibe-ic/skills/community-backlog-submit
Command: npx skills add https://github.com/vibeic/vibe-ic --skill community-backlog-submit-vibeic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a bug slips through the Vibe-IC plugin's gates and reaches RTL or hardware, fixing only that one bug leaves the plugin blind to the entire class of similar defects. This Skill captures the underlying general capability gap as a structured, IC-agnostic backlog item so the plugin can be hardened against the whole class of bugs. ## Core Features & Use Cases - Root-cause review workflow: Guides the agent to test existing gate programs against the buggy RTL and classify the gap as bug, issue, or enhancement. - Generality enforcement: Requires stripping all vendor, chip, and project-specific details so the backlog describes a reusable pattern, not a one-off defect. - Deterministic sanitization and compliance gates: Runs backlog_sanitize_check.py, defect artifact snapshotting, issue-body linting, and a final skill_compliance_check.py audit before any submission. - Use Case: After discovering that a wake-clear signal had only one reset path and the plugin's gate only warned, use this Skill to file a generalized enhancement backlog proposing the WARN be escalated to ERROR, optionally submitting it as a GitHub issue with user consent. ## Quick Start Ask the agent to record a community backlog item for the plugin gap just discovered in this design session and run the sanitize check before submitting.

Frequently Asked Questions about community-backlog-submit

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

FAQPage Schema
How do I report a plugin gap found during an IC design session?▼

Run the root-cause review to test existing gate programs against the buggy RTL, generalize the finding into a pattern, write a YAML file in community/backlogs/, then run backlog_sanitize_check.py. Submission to GitHub via gh issue create happens only with user consent.

What is the difference between a backlog item and a bug fix in this workflow?▼

The bug itself is still fixed on the design side, but the backlog records the general plugin capability that would catch the entire class of bugs next time. Backlogs describe patterns like missing gates or wrong severity levels, never a specific chip's defect.

Why must vendor and chip names be removed from backlog items?▼

Backlog items must describe general capability gaps that any agent designing a completely different IC would also hit. The sanitize gate flags chip names, vendor names, register maps, local paths, and other project-specific data as violations before submission.

Does the skill submit data to GitHub automatically?▼

No. Submission is optional and requires explicit user consent. If the user declines, the sanitized YAML file stays local and no data leaves the machine.

What happens to backlog YAML files created inside a git repository?▼

They must be either committed with an explicit git add or deleted; leaving them untracked is prohibited. The repo hygiene gate runs backlog_sanitize_check.py with --audit tracked and fails on any untracked backlog file.