Skill UI

This skill summarizes the current conversation into a structured handoff document, ideal for passing work to a fresh AI agent or starting a new session. It avoids content duplication by referencing existing artifacts (PRDs, plans, issues, commits) using their paths or URLs, ensuring the receiving agent has a concise and actionable overview of the project's state, open decisions, and next steps.

This tool manages isolated profiles for Codex CLI and Codex Desktop, ensuring that different accounts, projects, and local states do not interfere with each other. It provides dedicated CODEX_HOME directories, allowing users to securely switch contexts (e.g., work, personal, client) on a single machine without manual environment variable management.

A structured system for creating persistent journals that track project context, progress, and next steps. This method ensures that work survives session boundaries, allowing users to easily pick up where they left off, whether starting a session or winding down a project. It mandates clear entries detailing what was accomplished, the current state, and the immediate next action.

Automatically updates an existing handoff document by merging the current session’s progress. It intelligently applies specific merge rules to different sections: appending new history to 'Work Done' and 'Discoveries', while replacing volatile sections like 'Status' and 'Next Steps' to reflect the most current state. This ensures a comprehensive, chronological record of project advancement.

Summarizes the current workspace and reports fixture status, giving a quick overview of the project state for developers and teams.

This tool manages isolated profiles for Codex CLI and Codex Desktop, ensuring that different accounts, projects, and local states do not interfere with each other. It provides dedicated CODEX_HOME directories, allowing users to securely switch contexts (e.g., work, personal, client) on a single machine without manual environment variable management.

Validates Conductor workflow artifacts such as index, tracks, plans and status markers for completeness, consistency and correctness. Use after setup, before resuming a track, or when diagnosing stale or conflicting project state.

Resume interrupted project work by reconciling a saved handoff with current repository evidence: separate completed work, pending edits, superseded assumptions and blockers, then state the next verifiable action within existing authorization.