bill-feature-implement

Coordinates staged feature implementation from design doc to verified code, including PR description.

13|1|Updated Mar 16, 2026

Search Tags:#automation #workflow #planning #orchestration #telemetry #feature #code-review

Ready to run

npx skills add https://github.com/Sermilion/skill-bill --skill bill-feature-implement

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bill-feature-implement
Source: https://github.com/Sermilion/skill-bill/tree/main/skills/bill-feature-implement
Command: npx skills add https://github.com/Sermilion/skill-bill --skill bill-feature-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates and standardizes the end-to-end feature implementation process—from design doc to verified code—by coordinating planning, implementation, validation, and PR creation with a stable, auditable workflow.

Core Features & Use Cases

Orchestrates a multi-phase feature workflow (pre-planning, planning, implementation, completeness audit, quality check, and PR description) while keeping the orchestrator context lightweight.
Spawns specialized subagents for heavy phases and retains code-review responsibilities within the orchestrator.
Maintains telemetry ownership and a durable workflow-state contract for cross-agent consistency.
Use cases include implementing a feature from a design doc, handling scaling based on feature size, and restoring progress via continuation.

Quick Start

Provide a feature design doc and issue key to start an end-to-end implementation workflow.

Frequently Asked Questions about bill-feature-implement

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

FAQPage Schema

How do I automate end-to-end feature implementation from a design doc to verified code?▼

End-to-end feature implementation is automated by orchestrating staged phases from pre-planning to PR creation. The workflow spawns specialized subagents for heavy tasks while retaining code review in the orchestrator, ensuring strict contracts and telemetry ownership.

What is the best way to orchestrate a multi-phase feature workflow with code review?▼

Multi-phase feature orchestration runs through pre-planning, planning, implementation, completeness audit, quality check, and PR description. It keeps the orchestrator context lightweight by spawning subagents for heavy phases and conducting code review directly within the orchestrator.

How does a staged orchestration workflow handle scaling for features of varying sizes?▼

Staged orchestration handles scaling for varying feature sizes by coordinating subagents dynamically across implementation phases. It enforces strict contracts, validation, and telemetry ownership while maintaining a durable workflow-state contract for cross-agent consistency.

Can I restore progress via continuation if an automated feature implementation workflow is interrupted?▼

Progress restoration via continuation is supported through a durable workflow-state contract. This ensures cross-agent consistency and telemetry ownership, allowing the end-to-end feature implementation process to resume correctly after an interruption.

Do I need to provide a feature design doc and issue key to start the implementation workflow?▼

A feature design doc and issue key are required to start the end-to-end implementation workflow. These inputs trigger the staged orchestration pipeline, applying strict validation and artifact naming conventions across the pre-planning and implementation phases.

Why does the orchestrator retain code review responsibilities instead of delegating them to subagents?▼

The orchestrator retains code review to keep its context lightweight while maintaining quality control over the verified code. Subagents handle heavy implementation phases, while the orchestrator enforces strict contracts, validation, and telemetry ownership.