agents-configuration

Explains the agent harness loop's state machine, intake chain, and design intent for dispatched personas.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/tedeuxx/tadeumendonca-skills --skill agents-configuration-tedeuxx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agents-configuration
Source: https://github.com/tedeuxx/tadeumendonca-skills/tree/main/skills/agents-configuration
Command: npx skills add https://github.com/tedeuxx/tadeumendonca-skills --skill agents-configuration-tedeuxx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents working inside an AI-driven development loop often know what step comes next but not why the loop is shaped that way, so they act incorrectly in cases the state table does not enumerate. This Skill is the universal preload that carries the loop's intentional design — its intake chain, state machine, iteration axis, and inner-loop rules — to every dispatched persona. ## Core Features & Use Cases - State machine reference: Canonical transition table covering filed, description closed, ready, in progress, drafted, reviewed, and blocked states across product, content, and loop lanes, naming who acts and what artifact records each transition. - Loop model and mode selection: Guidance for choosing between gitflow-multi-env and trunk-single-env promotion models, and reading the scrum versus kanban mode from the record rather than inferring it from query output. - Design intent and discipline framing: Explains Agent Harness Engineering — mechanical gates over memory, the three surfaces (cadence, gates, harness-as-artifact), and when to dispatch agents-lead for machinery changes. - Use Case: When picking up a slice, proposing a change to the loop itself, or writing publicly about Agent Harness Engineering, load this Skill so decisions align with the loop's documented intent rather than ad-hoc judgment. ## Quick Start Ask the agent to apply the agents-configuration skill to explain which persona closes the description and applies the ready label for a loop-typed issue before dispatching any work.

Frequently Asked Questions about agents-configuration

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

FAQPage Schema
How do I decide who closes an issue description in this agent loop?

Consult the filed-to-description-closed rows in the states table: product lanes require product-lead and tech-lead together, content lanes close through product-lead alone, and loop lanes close through agents-lead alone with no exceptions.

What is the difference between loop model and loop mode?

The loop model defines how a change is promoted — gitflow-multi-env with an integration branch or trunk-single-env with one main branch. The loop mode defines how work flows — scrum where the container is a commitment, or kanban where it is only a label.

When should agents-lead be dispatched instead of tech-lead?

Dispatch agents-lead for any proposal about the loop machinery itself, before anything is built. Tech-lead never co-signs the loop lane's intake; that lane closes through agents-lead alone per the owner ruling recorded in the states table.

Does this skill define what ready or done means for an issue?

No. The readiness bar lives in the definition-of-ready skill and the done criteria in definition-of-done. This skill covers the mechanism — who acts at each transition and what artifact records it — not the bars themselves.

Why must the loop mode be read from the record instead of inferred?

The scrum and kanban pool predicates can return byte-identical empty results with opposite correct behaviors, so inferring the mode from query output fails silently. The mode must be read from docs/loop-mode.md before any pool query.