Plan Development

One private development plan, created once and revisited at its review points. Plans, completed learning and demonstrated capability stay distinct.

Contract

• Input: profile/ direction, skills, preferences and constraints; relevant project evidence; for a review, the current plan, the review period and what actually happened.
• Scope: Create or revise the plan; never declare planned learning achieved or publish it.
• Output: profile/development.md (or mapped plan): prioritized outcomes, actions, effort, evidence milestones, review points, and dated review entries.

Choose the branch

If no plan exists, or the user wants a new one, create. If a plan exists and the user reports progress or reaches a review point, review. Ask only when it is unclear.

Create

• Read the chosen direction, demonstrated experience and constraints. Ask only for missing priorities, time, budget or deadlines that change the plan. Assume no default goal (promotion, management, certification, a tech track); if direction is undecided, ask one question about the target or suggest reflect, and plan only against a stated direction.
• Separate demonstrated capabilities from aspirations. Keep gaps relevant to the chosen work; a job-ad requirement or peer credential is not automatically a gap.
• Prioritize a few outcomes by relevance and effort; state what is deferred. For each: a concrete action or experiment, approximate effort/cadence, observable completion evidence and a review point. Completing a course differs from demonstrating a skill.
• Fit time and budget with estimates. Check current official sources for specific courses or certifications, or label cost and availability unknown.

Review

• Read the plan, previous review and evidence for the period. Ask only for missing evidence that changes the assessment.
• Compare intended with actual: reported activity, completed learning, applied capability, externally corroborated results. Missing evidence means unknown, not failure.
• Explore blockers and changed priorities without blame; adjust scope or cadence, or suggest revisiting direction, rather than just adding effort. No percentage-complete or competence scores.
• Append a dated review entry; label superseded actions instead of deleting them. Propose factual profile updates for demonstrated outcomes separately (maintain-profile can apply them when installed).

Save

Ask where to save unless established; update the existing plan rather than creating a duplicate, and link it from the index Records when new. Do not schedule, enroll, purchase or publish without a request.

Done when

• Create: priorities trace to the direction and evidence-backed gaps; every action has effort, completion evidence and a review point.
• Review: progress is tied to evidence for a stated period, unknowns are explicit, and each change is justified and traceable to the plan.
• Plans, estimates and achievements stay distinct; save status is explicit.