feature-work

Implements new features end-to-end with tiered risk gating, atomic commits, and delegated CI monitoring.

2|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/witwave-ai/witwave --skill feature-work-witwave-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-work
Source: https://github.com/witwave-ai/witwave/tree/main/.agents/self/felix/.claude/skills/feature-work
Command: npx skills add https://github.com/witwave-ai/witwave --skill feature-work-witwave-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Autonomous agents need a disciplined, auditable process for shipping new features without bypassing human governance or breaking the build. This Skill enforces a single-pass feature workflow—read request, tier the risk, plan, implement, test, commit, and delegate push/CI—so feature work stays within an approved autonomy ceiling. ## Core Features & Use Cases - Risk-tier gating: Classifies work against a 1-10 tier ladder and routes anything above the autonomous ceiling (tier 3) to plan-only mode requiring human approval. - Non-waivable fix-bar: Requires tests, docs, atomic commits, and no scope creep before any commit lands; failures trigger revert and escalation. - Peer delegation: Hands push and CI watch to the iris peer agent, with fix-forward loops (max 2 attempts) and automatic tier demotion after triggered reverts. - Use Case: A user says "build a new MCP tool for log search"—the agent fetches the request, tiers it, writes a structured plan to feature_plans.md, implements with tests and docs in atomic commits, and delegates push plus CI monitoring. ## Quick Start Ask the agent to build a specific feature, for example: "felix, implement a health-check endpoint for the harness scheduler."

Frequently Asked Questions about feature-work

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

FAQPage Schema
How do I trigger an autonomous feature implementation?▼

Send a request like "build X" or "implement Y" via user A2A, zora dispatch, or a piper-routed GitHub Discussion. The agent reads the request, tiers the risk, plans, and implements if the tier is within the autonomous ceiling.

How does the risk tier ladder control autonomous feature work?▼

Work is classified on a 1-10 tier ladder by scope: tier 1 is a small single-file change, tier 3 is multi-file within a subsystem, and tier 6+ is architectural. Anything above the configured tier ceiling (default 3) becomes a plan-only draft requiring explicit human approval.

What happens when CI fails after a feature commit?▼

The iris peer reports failing-job logs and the agent enters fix-forward mode, applying fixes in new commits rather than amending. After two failed fix-forward attempts, all feature commits are batch-reverted and the failure is escalated for human review.

Can this skill handle bug fixes or architectural changes?▼

No. Bug fixes, gap-fills, doc maintenance, and releases belong to peer agents' lanes and are redirected. Architectural or breaking changes (tier 7+) produce a plan-only draft for human decision, never autonomous implementation.

Why does the agent refuse to commit on a dirty working tree?▼

A dirty tree means another process owns the tree state, so the agent stands down and surfaces the situation to escalations rather than committing on top of unknown WIP. It also refuses to ship features while CI on main is red.