founder-partner

To get proactive decision support, you need a partner mechanism that reads your founder context and cycle history. This skill surfaces honest observations and suggests the next action by maintaining a persistent founder-context.md file to track milestones across sessions.

Yes, a proactive partner adapts to technical, non-technical, and mixed founder workflows. It determines the appropriate partner mode by reading your context and history to complement your specific background and surface blind spots.

You need to establish a persistent founder-context.md file, along with your cycle and milestone data. These inputs allow the partner to orchestrate sessions, read your history, and update context with new session results.

Context continuity is maintained by updating the founder-context.md file with session results and milestones. This ensures the partner reads accurate history and cycle data to align focus and suggest the next skill for subsequent sessions.

A persistent founder-context.md file is required because it stores your history, cycle data, and milestones. Without it, the partner cannot read context, surface gaps, or update session results to orchestrate continuous decision guidance.