Skip to content

TS โ€” {PREFIX}-{N} / Phase {X}: {Title}

Date: YYYY-MM-DD Author: {author} Status: ๐ŸŸก TS_DRAFT โ€” Awaiting approval Parent HL: HL-{PREFIX}-{N}


1. Objective

{One paragraph: what this phase delivers and why it matters.}

2. Scope

In Scope

  • {what will be done}

Out of Scope

  • {what will NOT be done in this phase}

3. Principles Check

Map HL ยง7 principles to specific AC items. Each principle MUST have at least one AC enforcing it. If a principle has no applicable AC โ€” mark as "N/A" with reason.

# Principle (from HL ยง7) Enforced by Gate
P1 {principle name} AC-{N} {how verified}
P2 {principle name} N/A {reason not applicable}

4. Affected Files

File Action Description
path/to/file CREATE / MODIFY / DELETE {description}

Budget: {N} new files, {M} modifications. Defaults: max {max_files} files, max {max_new} new, max {max_loc} LOC.

5. Acceptance Criteria

Describe WHAT the result should achieve, not HOW to implement it. Each AC must be independently verifiable. Mark dependencies with [depends: AC-X]. Executor verifies dependent ACs in order โ€” a dependent AC cannot pass before its prerequisite.

AC-1:

{What the result should achieve โ€” 1-2 sentences.} - [ ] {Verifiable criterion} - [ ] {Verifiable criterion} Gate: {How to verify โ€” a command, query, visual check, or stakeholder confirmation}

AC-2: {title} [depends: AC-1]

{What the result should achieve โ€” 1-2 sentences.} - [ ] {Verifiable criterion} Gate: {How to verify}

6. Technical Guidance

Reference material, not instructions. Executor MAY deviate with justification in RF. - {Relevant context: where things are, what patterns exist, what constraints apply}

7. Definition of Failure

  • โŒ {Condition that causes RF rejection โ€” hard reject, not a warning}

8. Phase Risks

Risk Mitigation
{risk} {mitigation}

9. Cross-Phase Modifications (multi-phase only)

Include only for multi-phase tasks. Omit section entirely for single-phase tasks.

File Also modified in Coordination note
path/to/file Phase {what to watch for}

Cross-references: use Reference Format (e.g. [RF TFW-18](../../tasks/TFW-18__knowledge_consolidation/RF__PhaseB__knowledge_quality.md), D24, [TD-72](../tech-debt.md)). See compilable_contract.md ยง2. Build script resolves to hyperlinks.


TS โ€” {PREFIX}-{N} / Phase {X}: {Title} | YYYY-MM-DD