drivemind

Automate preservation of long-horizon work with YAML frontmatter and residue generation.

28|1|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/Yuzc-001/DriveMind --skill drivemind
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: drivemind
Source: https://github.com/Yuzc-001/DriveMind/tree/main/skill
Command: npx skills add https://github.com/Yuzc-001/DriveMind --skill drivemind

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

DriveMind preserves execution integrity, boundaries, continuity, and residue generation for long-horizon work, preventing degradation.

Core Features & Use Cases

  • Maintain objective and focus across sessions
  • Preserve boundaries and prevent unauthorized actions
  • Preserve continuity and enable safe handoffs
  • Produce reusable residue (lessons, next-time rules, memory)

Quick Start

Activate DriveMind for long-running tasks by defining the objective, blockers, and boundaries to enable safe, persistent work.

Frequently Asked Questions about drivemind

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

FAQPage Schema
How do I preserve context and prevent goal drift across long-horizon work sessions?

To preserve context and prevent goal drift, you can use a YAML frontmatter structure to define objectives, blockers, and boundaries, ensuring execution integrity is maintained across sessions over time.

What is the best way to handle context loss and enable safe handoffs for high-value projects?

Handling context loss and enabling safe handoffs requires preserving continuity through structured residue generation, capturing lessons and next-time rules to seamlessly resume high-value projects without degradation.

How do I generate reusable memory and lessons after completing long-running tasks?

You generate reusable memory by emitting compact residue upon task completion, which produces diary notes, actionable lessons, and next-time rules to prevent future continuity degradation.

Can I use YAML frontmatter to maintain boundaries and prevent unauthorized actions during execution?

Yes, you can use YAML frontmatter to define task boundaries and prevent unauthorized actions, ensuring that long-running execution strictly adheres to the original objective without boundary drift.

When do I need context preservation for managing boundaries and continuity risks?

You need context preservation when working on long-horizon tasks, high-value projects, or sessions with boundary risks, where goal drift, boundary drift, or continuity loss could severely degrade execution integrity.

Does context preservation work without setting up optional resource directories for scripts and references?

Yes, context preservation functions without optional resource directories, but configuring them for scripts, references, and assets enables on-demand task support and richer execution integrity for complex work.