skills.rest
c-sonnier
c-sonnierCOMMUNITY
Explore all skills by this author →
𝕏@c_sonnierGitHub

convergence-implement

Automate phase-based feature implementation with test-first verification checkpoints.

2|Updated Mar 31, 2026
Search Tags:#tdd#commit#verification#outline#phases#implement
One-click install
npx skills add https://github.com/c-sonnier/convergence --skill convergence-implement
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: convergence-implement
Source: https://github.com/c-sonnier/convergence/tree/main/plugins/convergence/skills/implement
Command: npx skills add https://github.com/c-sonnier/convergence --skill convergence-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Execute phase-based feature development with strict test-first rules and human checkpoints to ensure quality before progression.

Core Features & Use Cases

  • Phase-driven development: write tests first, implement, verify, and commit phase-by-phase with explicit checkpoints.
  • Guardrails: halts after 3 failed fixes and prompts human escalation.
  • Suitable for teams adopting outline-based workflows post-convergence-outline approval.

Quick Start

Begin the phase loop by writing a failing test for the first feature, then implement, verify, and commit in sequence.

Frequently Asked Questions about convergence-implement

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

FAQPage Schema
How do I implement features phase-by-phase with strict test-first verification?▼

Test-first verification requires writing a failing test for the initial phase, then implementing the code, verifying the test passes, and committing before progressing to the next outline phase.

What is an outline-driven workflow for test-first development?▼

An outline-driven workflow executes feature development sequentially through predefined phases, enforcing staged testing, implementation, and verification checkpoints with human approval before moving to the next stage.

Can I automate end-to-end feature implementation with commit verification checkpoints?▼

Yes, you can automate end-to-end feature implementation by enforcing a RED test first, followed by implementation, verification, and per-phase commits to ensure quality before progression.

How do I handle continuous test failures during phase-based implementation?▼

When test fixes fail consecutively, the implementation process halts after three failed attempts and prompts human escalation to resolve the issue before continuing.

Does this test-first implementation approach work for feature teams using outline approvals?▼

Yes, it is specifically designed for feature teams adopting outline-based workflows, assuming the development phases have already been approved during a prior convergence-outline stage.

Why do I need to commit after every phase in test-first development?▼

Committing after every phase creates discrete verification checkpoints, ensuring that each test-first implementation stage is validated and secured before the next phase begins.

Related Skills

Explore More Software Engineering Skills→
vertexcover-iovertexcover-io
4

brainstorm

Guide structured brainstorming and design-gate approval before coding begins.

Official
Advanced
hojinzshojinzs
16

push

Publish verified local commits to a remote Git branch with pre-push validation.

Community
Intermediate
baphledbaphled
1

check-compliance

Run linting, formatting, security scans, and tests before committing code.

Community
Intermediate
zhentingWu-wztzhentingWu-wzt
6

comet-build

Orchestrate software implementation with task planning, sub-agent delegation, and code execution.

Community
Advanced