Generate structured implementation plans with requirement traceability and QA gate configuration.
npx skills add https://github.com/ZaxbyHub/opencode-swarm --skill plan-zaxbyhub
Please help me install this Agent Skill. Skill: plan Source: https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/plan Command: npx skills add https://github.com/ZaxbyHub/opencode-swarm --skill plan-zaxbyhub
This Skill eliminates the risk of incomplete, non-compliant implementation plans that skip critical checks like spec alignment, requirement traceability, and QA gate configuration, which lead to rework, missed requirements, and failed implementations in AI coding workflows.
Use the plan skill to generate a compliant, gated implementation plan for your current project, aligned with your spec and pre-configured with all required quality controls.
High-intent search queries and answers about installing and using this skill.
To create a compliant implementation plan, you must map all spec requirements to tasks, resolve uncertainties through a clarification funnel, and configure QA gates before code generation. This eliminates coverage gaps and ensures traceability throughout the workflow.
Requirement traceability maps all functional requirements and MUST/SHALL obligations directly to planned tasks. This mechanism flags coverage gaps and gold-plating risks before implementation starts, ensuring no specification is missed during coding.
Configuring QA gates involves selecting quality controls like reviewer checks, test engineer verification, and security scans before dispatching tasks. This process persists execution profiles to enforce quality standards during parallel task execution.
Yes, external plan ingestion supports spec alignment by automatically checking existing specs and detecting stale content. It offers options to archive, update, or skip specs so your ingested plan matches current software requirements.
The best way to resolve planning uncertainties is using a structured 4-stage clarification funnel with a critic sounding board. This mechanism evaluates scope, security, and compatibility internally to reduce unnecessary user interruptions.
You need stale spec detection when generating new implementation plans or ingesting external ones. It ensures your current plan does not rely on outdated requirements by offering options to archive or update the spec content.
kimen-devScan feature specification documents for ambiguity and resolve gaps through interactive questioning.
exiaoCommunicate with AI coding agents via acpx for code generation, debugging, and reviews.
ZaxbyHubFilter non-critical clarification questions through a 4-stage funnel.
GustaPaesReviews software stories and produces quality gate decisions.
