Skills and availability

Skills are reusable instruction sets that teach an agent how to perform a particular kind of work. The plugin keeps one canonical skill tree and adapts how that tree reaches each host.

Skills are loaded on demand. Installing the plugin does not force every conversation through every skill or impose a fixed phase sequence.

Local catalog and published catalog

The repository contains 17 local skills. 16 are published as seedable Allye skills; setup is intentionally local because it describes installation and initial configuration rather than a normal workflow capability.

The local directory name and the published backend slug are usually the same, but not always. Use the backend slug when referring to a skill through Allye's skill tools.

Local skill	Published slug	Purpose
using-allye	using-allye	Bootstrap, capability detection, context policy, and skill routing
memory-protocol	allye-memory-protocol	Search, save, and link durable context
product-planning	allye-product-planning	Translate requirements into Epics, Features, and Stories
technical-planning	allye-technical-planning	Break a Story into tasks after discussing decisions and trade-offs
execution	allye-technical-development	Implement tasks with a read-first and TDD-oriented workflow
review	allye-technical-review	Review implementation against decisions and requested behavior
delivery	allye-technical-delivery	Verify and finalize a completed Story, including documentation and memory
tdd-workflow	allye-tdd-workflow	Red → Green → Refactor discipline and applicability checks
board-progression	allye-board-progression	Move work through a team's configured status pipeline
tools-quickref	allye-tools-quickref	Reference Allye tools and their actions
handover-protocol	handover-protocol	Transfer phase context between fresh conversations
sandbox	sandbox	Explore and research before committing to scope
orchestrator	orchestrator	Coordinate planned delivery, review, correction, and status cascade
verification-loop	verification-loop	Run a bounded test → fix → test loop before claiming completion
agent-runtime	agent-runtime	Contract for an optional external agent runtime and parallel dispatch
branch-landing	branch-landing	Decide how finished branch work lands and clean up safely
setup	local only	Initial plugin configuration and platform setup

The allye- prefix in several published slugs is intentional. It avoids collisions in the shared skill catalog; it is not a second implementation of the local skill.

Availability by platform

Platform	Skill delivery	Availability
Claude Code	Native plugin resources and MCP discovery	The local plugin includes all 17 skills. The published catalog provides the 16 reusable workflow skills.
OpenCode	Native package plus MCP discovery	The package embeds a subset for local prompt generation; the MCP connection is the path to the published catalog. Do not assume every skill is available offline.
Cursor	MCP discovery plus .cursorrules	The 16 published workflow skills are available through Allye when the MCP connection is authenticated. setup is not a remote skill.
Codex	MCP discovery plus AGENTS.md	The 16 published workflow skills are available through Allye when the MCP connection is authenticated. setup is not a remote skill.
Gemini CLI	MCP discovery plus GEMINI.md	The 16 published workflow skills are available through Allye when the MCP connection is authenticated. setup is not a remote skill.
Hermes Agent	Skills exported to disk by the adapter	16 skills are exported to Hermes' Allye skill directory. setup remains an installer-local skill.
Pi	Native package resource discovery	The package exposes the canonical skill tree, including the local setup skill.

Availability also depends on the current Allye connection and team scope. A host may have the integration installed while the MCP session is unavailable; in that case, the agent should report the limitation instead of presenting remote skills as loaded.

Workflow skills

Orientation and exploration

• using-allye establishes the adaptive toolkit, determines which capabilities exist, and routes the request to the smallest useful playbook.
• sandbox supports open-ended exploration and research before a direction or scope is committed.

Planning and delivery

• allye-product-planning turns approved product requirements into an Epic → Feature → Story structure.
• allye-technical-planning turns a Story into tasks after identifying ambiguities and presenting options with trade-offs.
• orchestrator coordinates an already planned delivery, including assignment, dispatch, review, correction, and status cascade.
• allye-technical-development implements tasks with read-first discipline, appropriate TDD, and bounded verification.
• allye-technical-review checks implementation quality and alignment with the requested behavior and locked decisions.
• allye-technical-delivery verifies the completed work, updates documentation when needed, and records delivery context.

Continuity and coordination

• allye-memory-protocol defines when to search and save durable context.
• handover-protocol defines the copyable contract between fresh workflow conversations.
• agent-runtime describes the optional runtime contract used when an external process manager is detected. It is not a universal requirement for parallel work.
• branch-landing guides the choice between merging, opening a pull request, or leaving a branch, followed by safe cleanup.

Quality and operations

• allye-tdd-workflow provides the Red → Green → Refactor method and a heuristic for deciding when it applies.
• verification-loop keeps verification bounded and evidence-based when a command fails.
• allye-board-progression explains how to respect a team's configured work-item pipeline without assuming universal column names.
• allye-tools-quickref is a lookup reference for Allye tools and actions.

Choosing a skill

The host should route by intent rather than by a hard-coded sequence:

• Explore an idea: sandbox.
• Define product scope: allye-product-planning.
• Break down an existing Story: allye-technical-planning.
• Implement a planned change: allye-technical-development.
• Review completed implementation: allye-technical-review.
• Finish and document delivery: allye-technical-delivery.

Supporting skills are loaded by those phases when useful. For example, execution can load verification-loop, while orchestration can use agent-runtime and branch-landing.

Team skills and local instructions

The plugin's catalog is the shared baseline. Teams can add their own skills, standards, templates, and checklists in Allye. An agent should discover relevant team guidance before making consequential changes and should suggest creating a standard when none exists, rather than inventing a permanent policy silently.