overnight

Automate overnight planning and handoff for backlog-driven development sessions.

1|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/charleshall888/cortex-command --skill overnight-charleshall888
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: overnight
Source: https://github.com/charleshall888/cortex-command/tree/main/plugins/cortex-overnight/skills/overnight
Command: npx skills add https://github.com/charleshall888/cortex-command --skill overnight-charleshall888

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Overnight skill enables autonomous planning and handoff of backlog-driven development sessions, turning manual coordination into a repeatable, auditable process that hands off execution to the runner.

Core Features & Use Cases

  • Eligibility checks to ensure backlog items have cortex/lifecycle/{slug}/research.md and spec.md and are not epic
  • Rendering a unified plan and inline specs for review before launch
  • Handoff to the runner with generated overnight-plan.md, overnight-state.json, and session.json
  • Single active overnight session at a time to avoid conflicts
  • Worktree-based integration flow to merge changes into a dedicated overnight/{session_id} branch

Quick Start

Run /overnight in Claude Code to start an autonomous overnight planning session that selects backlog items, generates a plan, and hands off to the runner.

Frequently Asked Questions about overnight

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

FAQPage Schema
How do I automate overnight planning and handoff for backlog-driven development sessions?

Automated overnight planning selects eligible backlog items, renders a unified plan with inline specs, and generates overnight-plan.md with session.json files for runner handoff.

What prerequisites are needed for autonomous backlog session planning?

Backlog session planning requires ready items with both research.md and spec.md artifacts in their lifecycle directory, and items must not be epic-level tasks to pass eligibility checks.

How does session management work for overnight development automation?

Overnight development automation enforces a single active session to avoid conflicts, using a dedicated overnight worktree and generating session.json to track state during runner execution.

Can I run multiple autonomous planning sessions simultaneously in Claude Code?

No, simultaneous autonomous planning sessions are unsupported because the system enforces a single active overnight session to prevent conflicts and ensure auditable runner handoff.

How are overnight development changes integrated into the main project?

Overnight development changes integrate through a worktree-based flow merging runner output into a dedicated overnight/{session_id} branch, keeping the main branch isolated until review.

What is the best way to review generated plans before overnight runner execution?

Reviewing generated plans before overnight runner execution is handled by rendering a unified plan with inline specs in Claude Code, allowing you to audit backlog selection and execution strategy before launch.