تشغيل أي مهارة في Manus بنقرة واحدة

tdd-workflow

النجوم١

التفرعات٠

آخر تحديث١٣ أبريل ٢٠٢٦ في ١٤:٤٤

TDD cycle process and design-check decision tree for feature implementation. Load when implementing features using test-driven development.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

woditschka

woditschka/confine-ai

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

محللو ضمان جودة البرمجيات والمختبرونمهن الحاسوب والرياضيات·SOC 15-1253

SKILL.md

readonly

name	tdd-workflow
description	TDD cycle process and design-check decision tree for feature implementation. Load when implementing features using test-driven development.
compatibility	["claude-code","opencode","github-copilot"]
metadata	{"version":"1.0","author":"team"}

For the full methodology — rationale, Red/Green/Refactor phase rules, and bug-fix discipline — see docs/tdd-principles.md. This skill is the condensed checklist loaded during implementation.

TDD Cycle

Plan — break the feature into TDD cycles. Write plan to .scratch/implementation-plan.md using the template in .claude/templates/implementation-plan.md.
Design check — before each cycle, verify the current design supports the behavior:
- Ready — proceed to Red.
- Small code gap — refactor first (keep tests green), then Red.
- Design gap — invoke system-design-expert. Wait for approval.
- Requirement gap — log in Feedback Log, invoke product-requirements-expert.
- Architecture misfit — stop, invoke system-design-expert with [ESCALATE].
Red — write a failing test.
Green — write minimum code to pass.
Refactor — clean up, keep tests green.
Next cycle — return to step 2.

Document Ownership

Never modify docs/prd.md or docs/system-design.md directly. Invoke the owning agent instead. Log all agent requests in the Feedback Log of .scratch/implementation-plan.md.

المزيد من هذا المستودع

نفس المستودع

design-validation

woditschka/confine-ai

Architectural validation checklist for feature approval. Load when validating that features fit into the existing architecture.

2026-04-171

adr-template

woditschka/confine-ai

Architecture Decision Record format, naming conventions, and when to create ADRs. Load when making or documenting architectural decisions.

2026-04-131

audit-agents

woditschka/confine-ai

Audit the agentic configuration for consistency, coherence, and conciseness. Load when modifying agent definitions, skills, or pipeline structure, or to verify cross-tool parity.

2026-04-131

code-quality-gate

woditschka/confine-ai

Build, test, format, and lint requirements that must pass before code review. Load when checking implementation completeness or running the quality gate.

2026-04-131

code-quality-review

woditschka/confine-ai

Go code quality checklist based on Google Go Style Guide. Load when conducting code quality reviews.

2026-04-131

commit-safety

woditschka/confine-ai

Pre-commit safety checks for secrets, credentials, local settings, and sensitive file patterns. Load before committing or when reviewing staged changes for accidental exposure.

2026-04-131

name	tdd-workflow
description	TDD cycle process and design-check decision tree for feature implementation. Load when implementing features using test-driven development.
compatibility	["claude-code","opencode","github-copilot"]
metadata	{"version":"1.0","author":"team"}

For the full methodology — rationale, Red/Green/Refactor phase rules, and bug-fix discipline — see docs/tdd-principles.md. This skill is the condensed checklist loaded during implementation.

TDD Cycle

Plan — break the feature into TDD cycles. Write plan to .scratch/implementation-plan.md using the template in .claude/templates/implementation-plan.md.
Design check — before each cycle, verify the current design supports the behavior:
- Ready — proceed to Red.
- Small code gap — refactor first (keep tests green), then Red.
- Design gap — invoke system-design-expert. Wait for approval.
- Requirement gap — log in Feedback Log, invoke product-requirements-expert.
- Architecture misfit — stop, invoke system-design-expert with [ESCALATE].
Red — write a failing test.
Green — write minimum code to pass.
Refactor — clean up, keep tests green.
Next cycle — return to step 2.

Document Ownership

Never modify docs/prd.md or docs/system-design.md directly. Invoke the owning agent instead. Log all agent requests in the Feedback Log of .scratch/implementation-plan.md.