Write phase state to `.devflow/state/<branch>/` and spawn a new session.
npx skills add https://github.com/AndreJorgeLopes/devflow --skill phase-handoff
Please help me install this Agent Skill. Skill: phase-handoff Source: https://github.com/AndreJorgeLopes/devflow/tree/main/skills/phase-handoff Command: npx skills add https://github.com/AndreJorgeLopes/devflow --skill phase-handoff
devflow phase-handoff prevents agents from continuing with stale or mixed context by capturing a deterministic frozen state at phase boundaries and starting the next phase in a clean session.
.devflow/state/<branch>/ with the current phase snapshot so the next session has an explicit, read-only entry point.mark_chapter (when available) to label the phase you’re leaving and sets a terminal title when possible.mcp__ccd_session__spawn_task to create a new Claude Desktop sidebar session with a stable, tool-triggerable slash command.In the current phase, run phase-handoff for your branch by providing --phase and --next-phase so it writes the frozen-state file and spawns the next-session with the correct first-line slash invocation.
High-intent search queries and answers about installing and using this skill.
To freeze Claude Desktop session context between development phases, the devflow phase-handoff captures deterministic state to disk and spawns a cold new session, preventing stale or mixed context from carrying over.
AI agents carry stale context when sessions persist across pipeline phases. Using a phase-handoff mechanism freezes the current state and spawns a clean session for the next phase, ensuring downstream decisions read only frozen artifacts.
You can spawn a new Claude Desktop session by calling mcp__ccd_session__spawn_task with a prompt whose first line is the next-phase slash command, creating a clean sidebar session for the next development phase.
Yes, git worktree supports AI session orchestration by allowing phase-handoff to write frozen state files to .devflow/state/<branch>/ for spec, plan, and lock-tests pipeline steps before spawning the next session.
The best way to prevent mixed context during AI development phase handoffs is to freeze the current phase state as a read-only markdown file and spawn a cold new session that reads only frozen artifacts from disk.
Yes, phase-handoff gates the session spawn behind a one-click user confirmation before calling mcp__ccd_session__spawn_task, ensuring deterministic control over when the next devflow phase begins.
AndreJorgeLopesExtend writing-plans to hand off plan state to the lock-tests phase.
abdias98Generate failing test files from DevFlow plan sections.
alchemiststudiosDOTaiDelegate coding tasks from Claude Code to Gemini CLI with verification.
j7-devSuggest manual context compaction at logical task intervals.