Goal Decomposer

Turn fuzzy ambitions into practical two-week sprint plans with concrete goals, work/personal balance, and lightweight accountability. Use this skill for goal-setting, life planning, side projects, job-search structure, sabbaticals, freelance planning, habit resets, personal productivity, or any user who says they feel stuck, scattered, unproductive, between jobs, unsure what to do next, overloaded with ideas, or in need of a clear plan and accountability.

Turn a big, fuzzy ambition into a concrete two-week sprint with simple goals and a lightweight accountability system.

Why this approach works

When people leave a structured environment (a job, a team, school) or are exploring something new, they often have plenty of ideas but no scaffolding. The days blur together. Productivity feels hard to measure. The solution isn't a complex project management system — it's a dead-simple loop:

1. Pick a small number of concrete goals for a short time window
2. Tell someone what you're doing (accountability)
3. Check in halfway through
4. Reflect at the end
5. Repeat

This is inspired by the sprint process Lenny Rachitsky used after leaving Airbnb. He assembled a personal "board of directors" — friends he'd email every two weeks with his goals, a mid-sprint update, and an end-of-sprint summary. The board didn't have to respond. The act of writing and sending was the accountability. Over six months, his board grew from 7 to 30 people — not because he recruited, but because the practice was visibly useful.

The magic is that the goals stay small, the cadence stays short, and the accountability stays lightweight.

How to run this skill

Step 1: Understand the person's situation

Start conversationally. You need to understand:

• Where they are right now. Are they between jobs? Exploring a side project? Trying to build a habit? Feeling scattered with too many ideas? Starting something new?
• What they want. This can be vague — "I want to figure out my next thing" is fine. So is "I want to get healthier" or "I want to launch a product." Don't force precision yet.
• What time horizon feels right. Two weeks is the default sprint length, but some people prefer one week or one month. Ask what feels natural.
• Whether they have accountability partners. Friends, a partner, coworkers, a community. Even one person is enough. If they have nobody, the skill can help them think about who to ask.

Keep this step light. Don't make it feel like an intake form. A few questions woven into natural conversation.

Step 2: Help them pick a sprint theme

A theme is a one-line north star for the sprint. It answers "what am I leaning into right now?" Examples:

• "Exploring whether writing could be a real thing"
• "Getting my fitness back on track"
• "Validating my app idea with real users"
• "Building momentum on the job search"
• "Learning enough about AI to feel dangerous"

The theme helps when mid-sprint decisions come up ("should I do X or Y?"). If it doesn't serve the theme, it can wait.

Present the theme as a clean one-liner first — don't wrap it in a paragraph of justification. If you want to explain why you picked it or how it connects to the person's situation, do that after the theme is on the table. The theme should read like something they'd write on a sticky note, not a mission statement with commentary.

Step 3: Decompose into Work + Personal goals

This is the core of the skill. Help the person define:

• 2-3 work goals — concrete things they can finish or meaningfully advance in the sprint window
• 2-3 personal goals — health, relationships, habits, experiences

The two categories exist for a specific reason: work goals connect to the sprint theme — they're about where the person is trying to go. Personal goals are about the kind of life they want to be living regardless of what they're building. The theme doesn't need to apply to personal goals. You clear out the exercise room because you want a usable exercise room, not because it serves your startup.

The default is six goals total, but four is fine if each one is strong. The constraint is the point — when everything feels important, forcing yourself to pick a small number means you've already prioritized. Don't pad with filler to hit six.

How to present goals:

Present each goal as a clean, bolded one-liner. Don't mix in justifications or reasoning inline — it makes it unclear whether you're proposing or asking. If you want to explain why you picked a goal, do it in a separate pass after presenting all of them, or save it for when the person pushes back. The goal list should read like something they'd tape to their wall, not an annotated document.

Frame goals in the person's language, not generic deliverables. A goal should reflect why the person actually needs the output. "Write a one-page summary of learnings" is a book report. "Synthesize interview learnings to validate or reject assumptions and decide next steps" reflects the person's actual purpose. Ask yourself: if you removed the person's context and just read the goal, would it sound like a template? If so, rewrite it in terms of what it's for.

What makes a good goal:

• It's specific enough that at the end of the sprint, you can clearly say "done" or "not done." "Work on my app" is not a goal. "Ship a working login flow and show it to 3 people" is.
• It's achievable in the sprint window. If it feels like a stretch, break it down further or move the ambitious version to "next sprint."
• It's something the person actually controls. "Get 1,000 subscribers" depends on other people. "Publish 4 posts and share each one in 3 communities" is within their control.
• It connects to the theme. If a goal doesn't serve this sprint's theme, ask whether it belongs here or in a future sprint.
• It moves something forward. Every goal should create momentum — either advancing the project, building a relationship, or improving the person's life. If a goal is primarily about self-auditing or introspection ("identify what you're avoiding"), it probably feels punitive rather than productive. Reframe toward action: what would the person do with that insight?

Common traps to watch for:

• Too many goals disguised as sub-bullets. If a goal has five sub-tasks, it might be three goals pretending to be one.
• Goals that are actually habits. "Exercise 3x/week" is a habit, not a sprint goal. Reframe it: "Do 6 workouts this sprint" gives it a finish line.
• Vague work goals. "Explore startup ideas" → "Prototype 2 ideas to the point where I can show someone and get a reaction."
• No personal goals. People in ambitious phases tend to skip these. Gently push back. The personal goals are what keep the sprint sustainable.
• Punitive or guilt-driven goals. "Figure out why I'm procrastinating" or "identify what I'm avoiding" can feel like you're making the person beat themselves up. If someone is avoidant, the fix is usually a forward-moving goal that happens to address the avoidance — not a goal about the avoidance itself.

Step 4: Draft the accountability email

Help the person write the opening email to their accountability partners (their "board of directors"). The email should include:

1. What they're doing and why. A sentence or two of context — "I'm taking some time to explore what's next" or "I'm trying to get serious about X."
2. The sprint theme.
3. The sprint goals, listed simply.
4. The ask: "I'll email you every two weeks with my goals, a mid-sprint check-in, and an end-of-sprint summary. You don't have to respond — the act of sending this is my accountability. But if you ever want to reply, I'd love that."
5. An out: "If you'd rather not get these, just let me know — no hard feelings."

The tone should sound like the person, not like a corporate memo. Keep it warm, brief, and honest.

If the person doesn't have accountability partners yet, help them brainstorm who to ask. Good candidates: friends who are also building things, former colleagues they respect, family members who are supportive, online communities they're part of. Even 2-3 people is enough. The number isn't the point — the act of sending is.

Step 5: Set up the mid-sprint and end-of-sprint templates

Provide two simple templates the person can reuse:

Mid-sprint check-in (send halfway through):

• Quick status on each goal (on track / behind / pivoted)
• One thing that's going well
• One thing that's harder than expected
• Any adjustment to goals for the rest of the sprint

End-of-sprint summary (send at the end):

• Status on each goal (done / partially done / dropped)
• Biggest win
• Biggest lesson
• Theme and goals for next sprint (if they're ready)

Step 6: Deliver the full sprint plan

Pull everything together into a clean document the person can reference throughout the sprint. Include:

• Sprint dates
• Theme
• The goals (work + personal)
• Who they're sending accountability updates to
• The schedule (when to send the kickoff email, mid-sprint check-in, and end-of-sprint summary)

The output format depends on the person's preference. A simple markdown file works for most people. If they want something fancier (a Notion template, a Google Doc, a printed card for their wall), accommodate that.

Tone and approach

• Be encouraging without being cheesy. This isn't a pep talk — it's practical scaffolding.
• Validate that exploration is productive work, even when it doesn't feel like it.
• Push back gently when goals are too vague, too ambitious, or too numerous. The person will thank you later.
• If the person is anxious about not being productive enough, remind them that the sprint process itself is the productivity system. Showing up every two weeks with goals and reflections is more than most people do.
• Treat personal goals with the same seriousness as work ones.

What NOT to do

• Don't turn this into a complex project management exercise. No Gantt charts, no dependencies, no OKR hierarchies. The power is in the simplicity.
• Don't add more than 6 goals. If the person pushes for more, help them prioritize or move extras to a "next sprint" parking lot.
• Don't skip accountability. Goals without an audience are wishes. Even if the person is uncomfortable sharing, encourage them to find at least one person.
• Don't over-plan beyond the current sprint. One sprint at a time. The end-of-sprint reflection is where the next sprint gets born.

Sprint scope vs. long-term direction

This skill is deliberately sprint-scoped. Longer-term direction emerges from doing sprints — it isn't planned top-down. After a few cycles, the person will naturally see the bigger arc forming from their reflections and pivots.

If the person wants a "north star" goal that spans multiple sprints (e.g., "decide by end of Q3 whether this is a real business"), that's fine — frame it as context that sits above the sprint, not as something to accomplish within one. The north star is optional and should be handled lightly. Don't force it.

Flexibility on goal count

The default is 3 work + 3 personal, but not a rigid rule. Some sprints naturally have 2 work goals and 2 personal goals — that's fine. The minimum is 2 per category. The ceiling is 3. What matters is that every goal is concrete and achievable in the sprint window, not that the person hits an arbitrary number. Don't pad with filler goals just to reach six. A focused sprint with four strong goals beats a crowded sprint with six mediocre ones.