code-team

Enforce spec-first TDD and security gates for code implementations.

6|1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/kouko/monkey-skills --skill code-team
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-team
Source: https://github.com/kouko/monkey-skills/tree/main/domain-teams/skills/code-team
Command: npx skills add https://github.com/kouko/monkey-skills --skill code-team

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduce the risk and cost of shipping code by enforcing spec-first development, test-first implementation, and primary-source-grounded quality gates so that features, fixes, and refactors are secure, maintainable, and reviewable.

Core Features & Use Cases

  • Spec-first workflows: Guide creation of TECH-SPEC.md, validate scope, and ensure implementations trace back to a spec.
  • TDD & test design: Produce failing tests first, implement minimal changes, and run refactor cycles (Red-Green-Refactor) with F.I.R.S.T test properties.
  • Automated quality gates: Trigger non-skippable security and architecture MUST gates and optional SHOULD gates (quality, spec consistency) via evaluator.
  • Legacy and refactor support: Use characterization tests and seam-based dependency-breaking techniques for safe refactors in untested code.
  • Use Case: Implement a new API endpoint by drafting a TECH-SPEC.md, generating unit tests, producing the minimal implementation, and passing security and architecture evaluations before merge.

Quick Start

Request implementation for the feature at path src/service with a TECH-SPEC.md, unit tests, and changes that pass the security and architecture gates.

Frequently Asked Questions about code-team

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

FAQPage Schema
How do I enforce spec-first TDD workflows for secure, maintainable production code?

Spec-first TDD workflows are enforced by drafting a TECH-SPEC.md, generating failing unit tests with F.I.R.S.T properties, and implementing minimal changes. This process ensures traceability and produces maintainable implementations through Red-Green-Refactor cycles.

What's the best way to safely refactor legacy code without unit tests?

Safely refactoring untested legacy code involves writing characterization tests and applying seam-based dependency-breaking techniques. This approach allows you to safely introduce changes and refactor cycles while minimizing regression risk in untested codebases.

How do automated security and architecture quality gates work during feature implementation?

Automated quality gates work by triggering non-skippable MUST gates for ASVS v5.0.0 security checks and SOLID architectural guidance, alongside optional SHOULD gates. An evaluator validates spec consistency and code quality before merge.

Can I use this approach to create a TECH-SPEC.md for a new API endpoint?

You can create a TECH-SPEC.md for a new API endpoint by requesting feature implementation at a specific path. The workflow drafts the spec, generates unit tests, produces the minimal implementation, and passes security and architecture evaluations.

Does spec-first development require unit tests to pass before architecture review?

Spec-first development requires passing unit tests during the Red-Green-Refactor cycle before architecture review. Non-skippable architecture MUST gates evaluate SOLID principles and refactoring guidance only after test-first implementation criteria are satisfied.