dev-impl

Enforce test-first TDD workflows with quality guardrails and confidence reports.

Updated May 5, 2026
One-click install
npx skills add https://github.com/seiei-sogen/tumigi --skill dev-impl-seiei-sogen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-impl
Source: https://github.com/seiei-sogen/tumigi/tree/main/skills/dev-impl
Command: npx skills add https://github.com/seiei-sogen/tumigi --skill dev-impl-seiei-sogen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill eliminates the risk of ad-hoc, untested code that leads to recurring bugs, rework, and inconsistent code quality by enforcing a strict test-first TDD workflow with built-in quality guardrails for every implementation task.

Core Features & Use Cases

  • Dual Execution Modes: Supports normal mode for implementing individual tasks from pre-defined development plans, and quick mode for lightweight fixes and adjustments without requiring a pre-built plan.
  • Built-in Quality Guardrails: Automatically enforces 500-line file limits, runs security and performance vulnerability checks, validates test coverage against project thresholds, and generates traffic-light confidence reports to flag areas needing human review.
  • Use Case: For example, when you need to implement a new user authentication endpoint as part of a planned development task, use this skill to write failing tests first, implement the code to pass those tests, run all required quality checks, and get a clear report of any design decisions that need human validation.

Quick Start

Use the dev-impl skill to implement the user profile update task from your project plan using test-first TDD with automatic quality checks.

Frequently Asked Questions about dev-impl

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

FAQPage Schema
How do I enforce test-first TDD workflows for bug-free code implementation?

Test-first TDD implementation enforces writing failing tests before code to eliminate ad-hoc coding and reduce bug rework. It guides you through writing tests, implementing code to pass them, and validating outputs against quality thresholds.

What's the best way to handle quick fixes without a full development plan?

Quick mode handles lightweight fixes and adjustments without requiring a pre-built development plan. It applies the same test-first principles and quality guardrails but skips planned task execution overhead for small changes.

Does TDD implementation work with complexity-based strategy selection?

Complexity-based strategy selection routes low, medium, and high complexity work into appropriate TDD workflows. This ensures implementation depth matches task difficulty while maintaining consistent code quality across all development tasks.

What quality guardrails are built into test-first implementation workflows?

Built-in quality guardrails enforce 500-line file limits, run security and performance vulnerability checks, validate test coverage against project thresholds, and generate traffic-light confidence reports flagging areas needing human review.

Can I use this for planned development tasks from a roadmap?

Normal mode implements individual tasks from pre-defined development plans using test-first TDD. It executes planned work items with automatic quality checks and confidence reporting for each implementation output.

Why does my code still have bugs after writing tests?

Ad-hoc coding without strict test-first workflows causes recurring bugs and rework. Enforcing TDD with vulnerability checks, coverage thresholds, and confidence reporting catches quality gaps that unstructured testing misses.