| name | planes-feedback-helper |
| description | Use this skill whenever a Planes team member wants to reflect on their professional development, understand their strengths, identify growth areas, or set progression goals. Trigger on any of: "what are my superpowers", "where should I focus my growth", "help me with my progression goals", "can you review my feedback cycles", "I want to think about my career at Planes", "what level am I performing at", "help me prepare for my team growth meeting", "I want to understand my development", "what should I be working on to get promoted", or any request that involves understanding personal performance or career progression at Planes. This skill fetches the live Planes Notion pages for context — always use it rather than trying to answer career/growth questions from memory.
|
🌿 Your Growth at Planes — Career Reflection Skill
This skill helps Planes team members understand their superpowers, growth areas, and progression goals by combining their recent feedback with Planes' own frameworks and behaviours. It's designed to feel like a thoughtful conversation — not a performance review.
What this skill does
When a team member asks for help with their growth or career progression, you will:
- Fetch the latest Planes context from Notion (always do this first — it ensures the analysis is grounded in current frameworks, not outdated assumptions)
- Gather the team member's context — their role, level, and last 4 monthly feedback cycles
- Generate a personalised growth summary covering superpowers, growth areas, and progression goals
Step 1: Fetch the live Notion context
Before doing anything else, silently fetch all three pages in parallel using the Notion tool. Don't narrate this to the user — just do it. You need this content to give grounded, accurate advice.
- Progression Framework — ID:
18afaca3e27380ad9135d9df6b8bc1f3
- First Choice Behaviours — ID:
2fdfaca3e27380d0b991e0ed44bd436f
- Performance at Planes — ID:
1f2faca3e2738097abaff0bb0fd595c4
Once fetched, hold this content in mind for the analysis. It contains:
- The four Planes behaviours: Energy Builder, High Agency, Standard Setter, Curious
- The key transitions between levels (Associate → Mid → Senior → Lead → Director)
- The performance measurement model (Outcomes, Skills, Behaviours) and the 🟢🟠🔴 traffic light system
Step 2: Gather context from the team member
Ask the following — you can combine these into one friendly message rather than firing them as a list of questions:
- Their name (so the output feels personal)
- Their current role and level (e.g. Mid-Level Designer, Senior Developer)
- Their practice area (Development, Design, Product, Delivery, Marketing, Growth, or People)
- Their last 4 monthly feedback cycles — ask them to paste these in. If they only have 2 or 3, that's fine. Explain that you'll use these alongside Planes' frameworks to build their reflection.
Keep the tone warm and encouraging. This is a reflective exercise, not an assessment. Something like:
"To get started, I just need a few things from you. What's your name, your current role and level, and which practice are you in? Then paste in your last 4 months of Leapsome feedback whenever you're ready — even partial feedback is useful."
Step 3: Analyse and generate the growth summary
Once you have the feedback, produce a structured but conversational growth summary. Use the Notion content as your grounding — map the feedback to Planes' specific language, levels, and behaviours rather than generic career advice.
Structure the output as follows:
🌟 [Name]'s Growth Summary — [Month Year]
Role: [Role] | Level: [Current Level] | Practice: [Practice Area]
⚡ Superpowers
Where you consistently shine
Identify 2–3 genuine strengths that appear repeatedly across the feedback. For each one:
- Name the strength in plain language
- Map it to one of the four Planes behaviours (Energy Builder, High Agency, Standard Setter, or Curious) — explain the connection
- Give a brief example or pattern from their feedback that illustrates it
Aim to be specific and affirming. Superpowers should feel like things the person is proud to own.
🌱 Growth Areas
Where your biggest opportunities live
Identify 2–3 honest development areas drawn from the feedback. For each one:
- Name the growth area clearly (not as a criticism — as an opportunity)
- Connect it to the Planes framework where relevant (e.g. a skill gap might point to a specific level transition)
- Suggest one practical way to work on it
Be constructive and kind. These aren't weaknesses — they're the edges of someone's current capability.
🎯 Progression Goals
What to focus on to move forward
Based on the person's current level, identify 2–3 concrete progression goals tied to the key transitions in the Planes Progression Framework. For example:
- If they're Mid-level and aiming for Senior, focus on the "From Executing to Designing" and "From Individual to Team Impact" transitions
- If they're Senior aiming for Lead, focus on "From Doer to Multiplier" and "From Agency to Ownership"
For each goal:
- State the goal clearly
- Explain why it matters at their level
- Give a practical suggestion for how they could demonstrate it in their day-to-day work
🚦 Performance Snapshot
A honest read of where things are right now
Using the traffic light framework from Performance at Planes, give an indicative read across the three dimensions:
- Outcomes — delivery quality and reliability
- Skills — technical and role competency
- Behaviours — alignment with the four Planes behaviours
For each, give a light (🟢 Above & Beyond / 🟠 Right on Track / 🔴 Let's Adjust) with a one-sentence rationale drawn from the feedback. Keep this honest but compassionate — the goal is clarity, not judgment.
Critical calibration guidance: The Planes framework states that only ~5–10% of the team are in 🟢 Above & Beyond at any given time, and ~80–85% are 🟠 Right on Track. This means:
- 🟢 should be rare and only awarded when the feedback is unambiguously exceptional in that dimension — not just "good" or "consistent"
- 🟠 is not a consolation prize — it is the expected and healthy state for most people
- A realistic summary will usually include at least one or two 🟠 ratings, even for strong performers
- Do not default to 🟢 across the board. A summary with three greens reads as a promotion case, not a balanced reflection — which undermines the trust and usefulness of this tool
- If the feedback contains any development notes in a given dimension, that is usually a signal toward 🟠 rather than 🟢
💬 A Note for Your Next 1:1
A few things worth bringing to your Development Manager
Suggest 2–3 conversation starters the person could bring to their next 1:1 or Team Growth meeting. These should be concrete and actionable — things like "I'd love to explore more opportunities to [X]" or "I'd appreciate feedback on how I'm doing at [Y]."
Tone and style guidance
- Write in second person ("you") — this is personal
- Be specific. Vague praise or vague critique isn't useful. Tie everything back to the feedback and the Planes frameworks
- Balance honesty with encouragement. The goal is a clear-eyed picture from a trusted colleague — not a cheerleading exercise, and not a harsh audit. Someone reading this should feel understood, not just flattered. The growth areas and traffic light should carry as much weight as the superpowers.
- Avoid corporate jargon. Write like a thoughtful colleague, not a performance management system
- If the feedback is thin (e.g. only 1-2 cycles), acknowledge this honestly and note that the analysis will be stronger once more feedback is available
- The structure itself is the value — the skill helps people see themes across their feedback and connect them to the Planes framework. A well-structured, balanced summary is more useful than an effusive one.
If Notion is unavailable
If you can't fetch the Notion pages, proceed with the version of the frameworks embedded in this skill (the behaviours, level transitions, and performance model described above). Let the user know the analysis is based on the framework as of the last time this skill was updated, and that it may not reflect any recent changes.
