plan-tdd

name

plan-tdd

description

Create or update source-tree TDD contract tests across unit, Component Test, and selected E2E verification units from an executable plan artifact whose `plan.md` and linked phase detail files follow the active plan wiki plan artifact contract, including first-work situations where the target app or test harness may not exist yet but Codex must still author failing/blocked TDD contract tests that gate plan completion, plus owner-test migration, selected browser journeys such as auth/session, redirect, cross-route, persisted browser state, and Korean-first TDD reports/test descriptions that keep English only for code, runner, schema, and exact identifier terms.

Plan TDD

Turn an executable plan artifact into source-tree tests and a plan-local TDD report without touching production code.

Required Reading

Read these references in order whenever this skill runs:

1. references/contracts.md for purpose, inputs, blocker taxonomy, report fields, output contract, and language rules.
2. references/workflow.md for test convention detection, clause extraction, classification, TDD authoring, validation, reporting, and completion checks.
3. references/guardrails.md for non-negotiable TDD authoring constraints.
4. references/test-authoring-conventions.md before creating or updating source-tree tests.
5. ../../plan-wiki/sync/current/core/common/용어-정책.md before writing report prose or test intent text.

Read these references only when the corresponding scope is active:

• references/unit-test-conventions.md when logic boundaries are in scope.
• references/component-test-conventions.md when component rendering, props/callbacks, form interaction, conditional UI, or same-screen UI synchronization is in scope.
• references/e2e-test-conventions.md when selected browser journeys or browser-only UI behavior are in scope.

Controller Rules

• Write or update test files only; never implement production code.
• Author only selected plan clauses and affected owner tests, not plan-adjacent regression coverage.
• Stop with an explicit blocker when the plan does not define enough contract, topology, runner, placement, or scenario detail.
• Write tdd.md as a helper artifact; keep source-tree tests as the durable source of truth.
• Use Korean-first report prose and test intent text while preserving exact commands, paths, identifiers, metadata keys, and test runner terms.