aibdd-core

Define a read-only reconciliation contract for cross-skill form skills.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/zenbuapps/zenbu-powers --skill aibdd-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aibdd-core
Source: https://github.com/zenbuapps/zenbu-powers/tree/main/skills/aibdd-core
Command: npx skills add https://github.com/zenbuapps/zenbu-powers --skill aibdd-core

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a centralized reconciliation contract and cross-skill reference patterns for form skills, enabling reuse of common definitions and workflows while keeping references read-only.

Core Features & Use Cases

  • Reconciler contract and shared pattern definitions used by all form skills (entity-spec, api-spec, bdd-analysis, feature-spec, activity-spec).
  • Serves as a read-only reference for other skills by providing access to files under references/.
  • Not directly triggering actions; acts as a shared guide loaded by other skills.

Quick Start

Review references/reconciler-contract.md to reuse standard reconciliation patterns in your skill.

Frequently Asked Questions about aibdd-core

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

FAQPage Schema
What is a reconciliation contract for cross-skill form skills?

A reconciliation contract defines shared pattern definitions and common workflows for form skills. It acts as a centralized, read-only reference that enables multiple skills to reuse standard definitions instead of duplicating logic.

How do I reuse standard reconciliation patterns in my skill?

To reuse reconciliation patterns, load the shared reference files from the references directory. Your skill reads these read-only contract definitions to apply standardized workflows rather than triggering actions directly.

Do I need a reconciler contract to use form skills like entity-spec or bdd-analysis?

Yes, form skills including entity-spec, api-spec, bdd-analysis, feature-spec, and activity-spec rely on a shared reconciler contract to maintain consistent desired-state definitions and cross-skill pattern alignment.

Can directly triggering actions be performed using this shared reference?

No, this shared reference cannot directly trigger actions. It serves strictly as a read-only guide loaded by other skills to access centralized reconciliation contracts and pattern definitions.

What's the best way to manage desired-state definitions across multiple form skills?

The best way to manage desired-state definitions is using a centralized reconciliation contract. This read-only reference provides shared pattern definitions that all form skills read to ensure consistency.

Why does my form skill need to read a shared reference instead of defining its own patterns?

Reading a shared reference prevents pattern duplication and ensures cross-skill consistency. The centralized reconciler contract provides standardized definitions so all form skills align without maintaining separate logic.