Orchestrate spec-driven AI feature workflows with DISCUSS, PLAN, and EXECUTE gates.
npx skills add https://github.com/hffmnnj/opencode-goopspec --skill goop-core
Please help me install this Agent Skill. Skill: goop-core Source: https://github.com/hffmnnj/opencode-goopspec/tree/main/skills/goop-core Command: npx skills add https://github.com/hffmnnj/opencode-goopspec --skill goop-core
GoopCore provides the essential operations for a disciplined, spec-driven development workflow, ensuring teams can consistently structure discussions, plans, execution, audits, and confirmations.
Describe a feature using the GoopSpec workflow's DISCUSS phase to gather requirements and begin planning.
High-intent search queries and answers about installing and using this skill.
Spec-driven workflows enforce disciplined phases: DISCUSS gathers requirements, PLAN locks specifications in SPEC.md, EXECUTE implements tasks, AUDIT verifies alignment, and CONFIRM gates acceptance. GoopCore implements these five phases with checkpoints and decision logs to maintain traceability across your entire feature delivery cycle.
Maintain traceability by enforcing locked specifications, wave-based task execution, and explicit acceptance checks through artifacts like SPEC.md and BLUEPRINT.md. GoopCore captures task-level checkpoints and decision logs at each phase, creating an auditable record of how requirements flowed into delivery.
Yes. Spec-driven planning enables product teams and engineers to coordinate by establishing shared specifications upfront, executing in defined waves, and validating against original intent. GoopCore provides gates between DISCUSS, PLAN, EXECUTE, AUDIT, and CONFIRM phases to ensure alignment before moving forward.
Locked specifications and execution blueprints prevent scope drift and misalignment in complex projects. Use them when teams require auditable execution cycles, multiple stakeholders must approve changes, or delivery must demonstrably match original requirements—common in regulated or high-stakes AI feature development.
Enforce gates by requiring explicit artifacts at each phase: SPEC.md locks requirements in PLAN, BLUEPRINT.md defines execution scope, and acceptance checks verify delivery aligns with specifications before proceeding. GoopCore structures these gates to prevent premature progression and ensure stakeholder sign-off.
getcrew44Produce outcome-driven product roadmaps with prioritized, dependency-aware epics.
Agile-VAutomate decision logging and requirement traceability for audit-ready compliance.
timothyshenOrganize specifications, plans, tasks, issues, ADRs, and change logs in a structured directory.
suhwanManage PDCA cycles from planning through improvement with phase-specific prompts and templates.
