skills.rest
ResearchMonkey
ResearchMonkeyCOMMUNITY
Explore all skills by this author →
GitHub

developer

Automate test-first feature implementation with quality gates and traceability.

Updated Apr 6, 2026
Search Tags:#tdd#traceability#code-review#developer#quality-gates#feature-implementation
One-click install
npx skills add https://github.com/ResearchMonkey/Foundation_template --skill developer-researchmonkey
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: developer
Source: https://github.com/ResearchMonkey/Foundation_template/tree/main/.agent/skills/developer
Command: npx skills add https://github.com/ResearchMonkey/Foundation_template --skill developer-researchmonkey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implementing new features, requirements, or bug fixes with a disciplined, test-first approach that ensures traceability and alignment with quality standards.

Core Features & Use Cases

  • TDD-driven development workflow: write failing tests first, then implement code to pass them.
  • Quality gates and documentation alignment: enforce linting, tests, and design-doc conformance before merge.
  • Traceability across requirements, tests, and implementation for auditability in product development.

Quick Start

Write a failing test for the new feature, then implement production code to pass the tests while satisfying all quality gates.

Frequently Asked Questions about developer

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

FAQPage Schema
How do I enforce test-first feature implementation with quality gates and traceability?▼

Test-first feature implementation with quality gates is automated by enforcing failing tests before production code, then validating acceptance criteria, documentation alignment, and risk checks throughout the delivery lifecycle for full traceability.

What is the best way to maintain traceability across requirements, tests, and code during bug fixes?▼

Traceability across requirements, tests, and implementation is maintained by automating the delivery workflow to enforce documentation alignment and acceptance criteria checks, ensuring auditability for product development and bug fixes.

How do I start a TDD-driven development workflow for a new feature?▼

To start TDD-driven development, write a failing test for the new feature, then implement production code to pass the tests while satisfying all built-in quality gates like linting and design-doc conformance before merge.

Can I use automated quality gates to enforce documentation alignment before merge?▼

Automated quality gates can enforce documentation alignment by validating linting, tests, and design-doc conformance before merge, ensuring all code-review requirements are met across teams and forks.

Does TDD-driven delivery work for both feature development and bug fixes across different forks?▼

TDD-driven delivery applies to requirements, bug fixes, and feature development across teams and forks, enforcing acceptance criteria and risk checks uniformly throughout the entire delivery lifecycle.

Related Skills

Explore More Software Engineering Skills→
infraspecdevinfraspecdev
3

implement-feature

Implement features with acceptance-criteria-driven development and test-first delivery.

Official
Advanced
JubaKitiashviliJubaKitiashvili
41

quality-gate

Run parallel code-reviewer and performance-profiler checks for React Native merges.

Community
Intermediate
danhannah94danhannah94

red-team

Stress-test design docs to surface gaps and lock decisions via Foundry.

Community
Advanced
Zenobia000Zenobia000
2

verification-loop

Automate multi-stage pre-merge code quality validation for JavaScript, TypeScript, and Python projects.

Community
Intermediate