long-running-harness

Cross-session context maintenance requires persistent artifacts and structured orchestration. This harness generates features.json, progress.md, and architecture.md during initialization, then applies them at the start of each new session to restore project state, track completed work, and resume development without rebuilding context.

Long-running projects need deterministic handoffs and progress tracking. Initialize the harness with your project scope to generate structured artifacts that document features, architecture, and session progress. The harness applies these artifacts at each session start to enable seamless continuation and prevent project drift.

Session continuity depends on persisting state across runs via structured artifacts. The harness manages multi-session development by maintaining a features list, progress log, and architecture documentation that carry forward between sessions, eliminating repeated setup and ensuring consistent project direction.

Yes. The harness handles complex projects by managing feature handoffs, session orchestration, and progress governance across multiple phases. It satisfies functional and technical requirements for generating structured project artifacts and coordinating development via defined orchestration flow and allowed tools.

The harness generates three core artifacts: features.json (enumerated feature scope), progress.md (session-by-session status log), and architecture.md (structural decisions). These structured outputs persist across sessions and enable what's-next queries without rebuilding context from scratch.