aibdd.discovery

Orchestrate specification discovery across activities, features, APIs, and entity models.

1|Updated Apr 20, 2025

Search Tags:#api #specification #requirements #discovery #coordination #bdd #entity

Ready to run

npx skills add https://github.com/j7-dev/wp-power-checkout --skill aibdd-discovery

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aibdd.discovery
Source: https://github.com/j7-dev/wp-power-checkout/tree/main/.github/skills/aibdd.discovery
Command: npx skills add https://github.com/j7-dev/wp-power-checkout --skill aibdd-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill acts as the central orchestrator for all specification views, ensuring consistency and managing the discovery process for requirements. It bridges the gap between strategic business goals and tactical technical implementation.

Core Features & Use Cases

Unified Specification Management: Coordinates activities, features, API definitions, and entity models.
Two-Phase Discovery: Operates in 'strategic' and 'tactical' modes to progressively refine specifications.
Consistency Enforcement: Guarantees that all specification artifacts remain synchronized throughout the development lifecycle.
Use Case: When a new feature idea is proposed, this Skill guides the user through defining high-level activities, then drills down into detailed feature specifications, API endpoints, and database schemas, ensuring all aspects align.

Quick Start

Initiate a new specification discovery process by providing a user idea.

Frequently Asked Questions about aibdd.discovery

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

FAQPage Schema

How do I coordinate API specifications with feature requirements and entity models?▼

Specification coordination is achieved by orchestrating activities, features, API definitions, and entity models, ensuring all artifacts remain synchronized and consistent throughout the development lifecycle.

What is two-phase specification discovery for requirements management?▼

Two-phase discovery operates in strategic and tactical modes to progressively refine specifications, bridging strategic business goals and tactical technical implementation by drilling down from high-level activities into detailed features and schemas.

How do I start defining API specifications and entity-relationship diagrams from a new feature idea?▼

Initiate the discovery process by providing a user idea, which guides you through defining behaviors, features, API specifications, and entity-relationship diagrams based on existing specifications to ensure alignment.

How can I enforce consistency across multiple specification views during development?▼

Consistency enforcement works by managing cross-view updates and guardrails across activities, features, API definitions, and entity models, guaranteeing all specification artifacts remain synchronized throughout the lifecycle.

Do I need existing specifications to use this two-phase discovery approach?▼

No, you can define behaviors, features, API specifications, and entity-relationship diagrams based on both new user input and existing specifications, allowing you to start from a fresh idea or coordinate current artifacts.