tdd-context-retainer-orchestrator-01

스타10

포크3

업데이트2026년 4월 11일 06:45

Retain and orchestrate context for long-running TDD work by tracking red, green, and refactor state, test status, implementation progress, and resumable next steps in a structured progress journal. Use when sessions span interruptions, multiple files or crates, or frequent context switches and Codex must produce reliable handoffs and resume points.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

that-in-rust

that-in-rust/agent-room-of-requirements

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Tdd Context Retainer Orchestrator 01

Use this skill to preserve continuity in long TDD efforts and provide deterministic resume context across interruptions.

Workflow

Initialize a journal once per workstream.

Run scripts/progress_journal_orchestrator.py init.
Store one journal per feature or ticket.

Capture checkpoint updates continuously.

Run scripts/progress_journal_orchestrator.py update after each meaningful change:
Test batch created or changed.
Phase transition (Red, Green, Refactor).
Multi-file or multi-crate edits.
Performance or error regression discovery.

Resume work from the last saved state.

Run scripts/progress_journal_orchestrator.py snapshot.
Use the latest checkpoint to restore current phase, failing tests, implementation status, and next action.

Emit handoff summaries.

Produce a short human-readable status with:
current phase
top three next steps
blockers
unresolved design decisions

Journal Contract

Capture these sections in every checkpoint:

Current Phase
Tests Written
Implementation Progress
Current Focus
Next Steps
Context Notes
Performance/Metrics

Use explicit identifiers when available:

test names
file paths
function signatures
error messages

Script Usage

python3 scripts/progress_journal_orchestrator.py init \
  --path journals/feature-a.md \
  --task "Feature A end-to-end TDD"

python3 scripts/progress_journal_orchestrator.py update \
  --path journals/feature-a.md \
  --phase Red \
  --focus "Write failing tests for endpoint validation" \
  --test "test_endpoint_rejects_empty_payload|failing|expects 400 on empty payload" \
  --implementation "api/handlers.rs: added request parser scaffold" \
  --next-step "Implement minimum handler logic to satisfy validation tests" \
  --note "Need shared fixture helper for request setup"

python3 scripts/progress_journal_orchestrator.py snapshot \
  --path journals/feature-a.md

Guardrails

Never leave Next Steps empty.
Track why for major decisions, not only what.
Record cross-component dependencies explicitly.
Keep updates small and frequent to reduce context drift.
Prefer append-only checkpoints over rewriting history.

Context Strategy

Load progressively:

Load this SKILL.md.
Load Journal schema and examples.
Load Checkpoint cadence playbook for long-running sessions.
Load Resume and handoff prompts when resuming or transferring work.

References

이 저장소의 다른 Skills

같은 저장소

strata-202607

that-in-rust/agent-room-of-requirements

Use Strata, the Legacy Code Labs macOS visual-spec app, through its local Streamable HTTP MCP server. Trigger when Codex needs to create, read, validate, update, version, diff, or restore Strata diagrams; build visual specs from user flows, discovery trees, architecture sketches, or D2; diagnose Strata MCP setup; or verify a feature against a shared Strata canvas.

2026-07-1610

clarity202606

that-in-rust/agent-room-of-requirements

Use Clarity, the LegacyCodeHQ structural design CLI, for dependency impact graphs, architecture/refactoring verification, before-commit design checks, code review context, cycle/module/workspace exploration, AGENTS.md Clarity setup, or rebuilding/probing Clarity command availability. Use when Codex needs to run or interpret clarity show, watch, languages, extensions, modules, cycles, workspace, setup, or version-specific Clarity commands.

2026-07-0810

kotlin-backend-delivery-01

that-in-rust/agent-room-of-requirements

Plan, build, harden, and review Kotlin backend services with Spring Boot, Ktor, coroutines, typed configuration, persistence, migrations, testing, security, resilience, and operations. Use for Kotlin HTTP APIs, workers, service refactors, production-readiness reviews, or JVM backend architecture decisions.

2026-07-0510

kotlin-coder-01

that-in-rust/agent-room-of-requirements

Reliability-first Kotlin skill for implementing, refactoring, or reviewing Kotlin libraries, CLIs, JVM modules, shared domain code, coroutine code, and Java interop boundaries. Use when work needs null-safety discipline, value and sealed types, idiomatic scope-function use, typed errors, structured concurrency, testing, or JVM quality gates.

2026-07-0510

python-coder-01

that-in-rust/agent-room-of-requirements

Reliability-first Python skill for implementing, refactoring, or reviewing Python packages, CLIs, services, scripts, async code, tests, and typed modules. Use when work needs type hints, dataclasses, boundary parsing, exception design, context managers, asyncio cancellation, packaging, pytest or unittest strategy, ruff, mypy, pyright, or runtime safety.

2026-07-0510

local-vision-ollama

that-in-rust/agent-room-of-requirements

Analyze images using local Ollama vision model (qwen3.5:4b) with automatic pre-resizing and filename sanitization for reliable processing.

2026-05-1010

name	tdd-context-retainer-orchestrator-01
description	Retain and orchestrate context for long-running TDD work by tracking red, green, and refactor state, test status, implementation progress, and resumable next steps in a structured progress journal. Use when sessions span interruptions, multiple files or crates, or frequent context switches and Codex must produce reliable handoffs and resume points.