software-development

Routes development tasks to analyst, developer, debugger, coding-agent, or code-reviewer roles in Git repositories.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/coferlandia/coferlandia-skills --skill software-development-coferlandia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: software-development
Source: https://github.com/coferlandia/coferlandia-skills/tree/main/skills/engineering/software-development
Command: npx skills add https://github.com/coferlandia/coferlandia-skills --skill software-development-coferlandia

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Coordinating AI agents on real codebases often leads to blurred responsibilities: agents plan and implement at once, review their own work, or commit without authorization. This Skill enforces explicit role separation, bounded Git authority, and traceable handoffs so development work stays supervised and auditable. ## Core Features & Use Cases - Role Routing: Directs each request to exactly one role—analyst, developer, debugger, coding-agent, fix-agent, or code-reviewer—based on request signals, with a fast Retouch Mode for trivial localized changes. - Architecture Gate Enforcement: Blocks analysis and implementation until a required architecture gate in the work contract reports Status: passed, preserving the Architect Addendum. - Controlled Git Authority: Standalone roles never commit or merge without direct human authorization; in orchestrated mode the project-orchestrator owns all Git lifecycle operations. - Use Case: A user asks to fix a regression in a Git repository. The Skill routes to the debugger role, which reproduces the failure, identifies the root cause, implements a minimal fix with regression tests, and hands off uncommitted work to a distinct code-reviewer with a suggested commit message. ## Quick Start Ask the agent to implement a feature or fix a bug in your repository and it will select the appropriate development role, follow the gated workflow, and hand off reviewed work with a suggested commit message.

Frequently Asked Questions about software-development

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

FAQPage Schema
How do I route a coding task to the right AI agent role?▼

The Skill selects one role from request signals: analysis requests go to analyst, detailed executable contracts to coding-agent, bugs to debugger, features to developer, and review requests to code-reviewer. Retouch Mode is checked first for trivial localized changes.

Can an AI agent commit or merge code without human approval?▼

No. Standalone development roles never stage, commit, merge, or push by default. A standalone code-reviewer may commit only after a direct, current human instruction, and in orchestrated mode only the project-orchestrator controller owns Git operations.

What is Retouch Mode and when does it apply?▼

Retouch Mode handles small, unambiguous, low-risk changes without formal planning, worktrees, or reviewer handoff. It is excluded for public APIs, schemas, migrations, security boundaries, concurrency, CI/CD, and other shared or high-risk surfaces.

Does this workflow require GitHub to work?▼

No. GitHub is optional for Analyst and coding-agent execution. When GitHub is unavailable, the Skill uses local fallback contracts stored under the .agent/ directory with EPIC.md, ANALYSIS.md, and task files.

What happens when an architecture gate is not passed?▼

When a work contract contains an Architecture Gate with Mode: the-architect, only Status: passed permits analysis or implementation. The agent stops before production changes and returns unresolved or conflicting gates to the control authority.