harness-session-start

Initializes agent sessions by discovering project state, quality gates, and active tasks.

Updated Jul 29, 2026
One-click install
npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill harness-session-start-maicongambini
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-session-start
Source: https://github.com/MaiconGambini/opencode-harness-guide/tree/main/skills/harness-session-start
Command: npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill harness-session-start-maicongambini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding agents lose context between sessions, forcing developers to manually re-explain project state, active tasks, and quality status at the start of every session. ## Core Features & Use Cases - State Discovery: Locates progress files, feature specs, and handoff documents across multiple conventional paths (.specs/, agent-os/, docs/harness/) without repo-specific assumptions. - Quality Gate Awareness: Reads quality thresholds and the latest gate report so sessions never start new feature work on top of a red or stale quality posture. - Task Declaration: Selects exactly one active task and outputs a standardized status line with acceptance criteria and quality metrics. - Use Case: A developer opens a new OpenCode session on a long-running project; the skill reads the handoff, finds the in-progress spec tickets, checks the mutation-testing gate, and declares the active task automatically. ## Quick Start Start my session by discovering the project state, quality gate status, and active task using the harness session start procedure.

Frequently Asked Questions about harness-session-start

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I restore agent context at the start of a new coding session?

Run the session start sequence, which reads root instructions, locates progress state in priority order, reads the handoff document, and declares one active task with acceptance criteria. This reconstructs context without manual re-explanation.

How does the skill find project state files?

It searches prioritized locations: `.specs/project/STATE.md`, `docs/harness/progress.md`, then `agent-progress.md` for progress, and `feature_list.json` or `agent-os/specs/` for feature state. If none exist, it recommends running harness-init.

What happens when the quality gate is red at session start?

A red gate posture is stated first and becomes the active task unless the operator overrides it. This prevents starting new feature work on top of failing quality metrics, which would make the red state permanent.

Does the session start skill require specific files to exist?

No, it makes no repo-specific assumptions and does not require `init.ps1`, `feature_list.json`, or `.specs/project/STATE.md`. Missing state is reported explicitly, and a missing quality report is treated as unconfigured rather than green.

When does the session start sequence abort?

It aborts when the startup command fails, when existing progress or feature state is unreadable, or when more than one task is marked in_progress. A broken quality gate (exit 2) is reported as a blocker but does not abort the session.