session-start

To bootstrap a development session, the Skill parses repository state from git, reads workplan markdown files, and queries open GitHub issues to present a concise session goal. It summarizes the current phase, completed tasks, and next steps for confirmation before taking action.

Tracking editorial workflow progress involves reading the latest DEVELOPMENT-NOTES.md entry and feature workplans to capture accomplishments, failures, and course corrections. This process surfaces top unresolved items and guiding priorities to establish a clear session goal and context.

Session management integrates GitHub issues by querying open issues via gh to surface unresolved items, then reading local DEVELOPMENT-NOTES.md and workplan files. It combines this repository state to report a session goal, expected outcomes, and top actions back to the user.

Yes, this session-start workflow is applicable when planning editorial or feature work in a git-driven project. It specifically scopes worktrees and feature folders located in docs/1.0/001-IN-PROGRESS alongside DEVELOPMENT-NOTES.md and GitHub issues to parse repository state.

Yes, querying open GitHub issues to surface top unresolved items requires the gh CLI. The session bootstrapping process depends on gh to check open issues and parse repository state from git before presenting a session goal.

The session goal requires confirmation to ensure the parsed repository state, markdown summaries, and open issues accurately reflect the current context. This validation step prevents incorrect actions by verifying the gathered workplan and development notes align with user expectations.