aidd-core

Aggregate canonical Python entrypoints under skills/*/runtime for cross-skill navigation.

5|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/GrinRus/ai_driven_dev --skill aidd-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aidd-core
Source: https://github.com/GrinRus/ai_driven_dev/tree/main/skills/aidd-core
Command: npx skills add https://github.com/GrinRus/ai_driven_dev --skill aidd-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aggregates access to shared runtime entrypoints and cross-skill ownership references, reducing fragmentation across multi-skill workflows.

Core Features & Use Cases

  • Canonical entrypoint hub: exposes shared runtime entrypoints under skills/*/runtime for cross-skill coordination.
  • Ownership guidance: links to policy boundaries and domain owners to simplify governance.
  • Stage navigation: serves as a central hub for navigation between idea ↔ research ↔ plan across skills.

Quick Start

Start by referencing the canonical Python entrypoints listed in this SKILL.md to route requests through the shared runtime.

Frequently Asked Questions about aidd-core

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

FAQPage Schema
How do I coordinate shared runtime entrypoints across multiple Python skills?

Centralize navigation by routing requests through canonical Python entrypoints listed in SKILL.md, which exposes shared runtime paths under skills/*/runtime to resolve cross-skill ownership and reduce workflow fragmentation.

What is the best way to resolve canonical entrypoints for cross-skill workflows?

Resolve canonical entrypoints by referencing consistent ownership policies documented in SKILL.md, ensuring that cross-skill coordination routes through the shared runtime paths established under skills/*/runtime.

How do I navigate between idea, research, and plan stages across different skills?

Navigate between idea, research, and plan stages by using the centralized hub to route requests, linking stage transitions across skills through the shared runtime entrypoints and ownership boundaries defined in SKILL.md.

Do I need consistent ownership references in SKILL.md to use cross-skill navigation?

Yes, consistent references to ownership in SKILL.md are required to accurately resolve canonical Python entrypoints and maintain governance boundaries across cross-skill workflows within the shared runtime.

Can I use a centralized hub to manage policy boundaries and domain owners for Python workflows?

Yes, the centralized navigation hub links to policy boundaries and domain owners, simplifying governance and routing for Python workflows by aggregating access to shared runtime entrypoints across related skills.