agentdev-project-extensions

Resolves project-specific YAML extensions for workflow and capability skills at runtime.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/yogata/agent-dev-flow --skill agentdev-project-extensions-yogata
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agentdev-project-extensions
Source: https://github.com/yogata/agent-dev-flow/tree/main/src/opencode/skills/agentdev-project-extensions
Command: npx skills add https://github.com/yogata/agent-dev-flow --skill agentdev-project-extensions-yogata

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires zod, and includes scripts (resource) components.

What problem does it solve? Distribution commands and skills must stay project-agnostic, yet real projects need their own context, rules, checks, acceptance gates, and prohibitions applied at runtime. This Skill resolves the matching project extension file under .agentdev/extensions/skills/ so project-specific behavior is injected without modifying distribution bodies. ## Core Features & Use Cases - Extension Discovery and State Classification: Locates the single extension file matching the calling skill and classifies it as missing, malformed, migration-required (legacy kind), schema-violation (unknown kind), or valid, applying the correct stop or fail-open behavior for each state. - Five-Section Reading: Reads context, rules, checks, acceptance_gates, and must_not sections as additions to standard behavior, never as replacements, in the order Workflow Extension, internal Workflow Extension, Capability Skill Extension. - Delegation Extraction: Extracts project-local skill delegation targets from rules and checks entries that declare a skill field. - Use Case: A project defines .agentdev/extensions/skills/case-run.yaml with extra checks and a must_not list; when the case-run workflow skill executes, this resolver loads that extension, validates its kind literal, and applies the added gates before completion. ## Quick Start Ask the agent to load the project extension for the current workflow skill from .agentdev/extensions/skills and apply its context, rules, checks, acceptance gates, and must_not entries.

Frequently Asked Questions about agentdev-project-extensions

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

FAQPage Schema
How do I add project-specific rules to a distribution skill without editing it?▼

Create a YAML file at .agentdev/extensions/skills/{skill-name}.yaml with kind workflow-extension or capability-skill-extension and fill the context, rules, checks, acceptance_gates, and must_not arrays. The resolver loads it at runtime as an addition, never replacing standard behavior.

What happens when a project extension file is missing or malformed?▼

A missing extension is a normal state and standard behavior continues. A malformed extension (YAML syntax error or missing required fields) triggers an error message, is ignored, and execution continues fail-open with an empty extension.

Which extension kind values are valid in AgentDevFlow?▼

Only three kind literals are valid: workflow-extension, internal-workflow-extension, and capability-skill-extension. Legacy kinds command-extension and skill-extension stop processing as migration-required, and any other value stops as a schema violation.

Can a capability skill read a workflow extension file?▼

No. Capability skills read only their own capability-skill-extension file, and workflow skills never read capability-skill-extensions. Public workflow extensions are not implicitly copied to capability skills; application order is workflow, internal workflow, then capability skill extension.

How does the resolver delegate work to project-local skills?▼

Rules and checks entries may include a skill field naming a project-local skill. The resolver extracts these as delegation targets, but the delegated skill's implementation is entirely the applying project's responsibility.