Artificial Idea | AI careers · practical prompts · no hype Thursday, December 25, 2025 · Issue #42 · Prompt Tutorial

The ninety-day plan

Your 2026 AI toolkit: 10 prompts to start the new year smarter

Most development plans are made in good faith and abandoned by February. The ones that survive are built differently. Here is how to build one that survives.

Monday's issue mapped six emerging roles created by the AI transition and identified what each one requires from the professionals targeting it. This issue delivers on the promise made at the end of that piece: a structured prompt framework for turning that role mapping into a ninety-day development plan that is specific enough to act on, honest enough to survive contact with a real working week, and grounded in the data this newsletter has been building since August rather than in the generic annual goal-setting that produces the same abandoned resolutions every January.

The framework takes approximately forty minutes to run in full. The plan it produces is not a document to be filed. It is a working instrument to be used, adjusted, and returned to at thirty-day intervals. The distinction between those two things is the distinction between development plans that produce results and those that produce good intentions.

Why most development plans fail by February

The research on this is consistent and has been consistent for decades. A 2024 meta-analysis by the American Psychological Association reviewing forty-three studies on professional development plan follow-through found that the single strongest predictor of plan abandonment was not motivation level at the time of making the plan. It was the specificity of the implementation intention: the degree to which the plan answered not just what the person intended to do but when, where, and how they intended to do it.

Plans that answered all four questions showed follow-through rates three times higher than plans that answered only the first. The professionals who abandoned their plans in February were not less motivated than those who continued. They had made plans that left too many decisions unmade, decisions that accumulated as friction in the early weeks until the friction exceeded the momentum and the plan stopped.

The framework below is designed around this finding. Every prompt is oriented toward specificity of implementation rather than ambition of outcome. The plan it produces will not be the most impressive development plan you have ever written. It will be the one most likely to be running in March.

Prompt 1: The role fit assessment

Before building a plan, you need to know which of the six roles from Issue #41 is the right target for your specific combination of current capabilities, professional context, and career objectives. This prompt makes that assessment specific rather than aspirational.

You are a career strategist helping me identify 
the most strategically sound development target 
from a specific set of emerging professional roles.

My current professional profile:
Role and function: [describe what you actually do]
Industry and sector: [describe your context]
Years of experience and seniority level: [be honest]
Current AI capability level: [1 to 10, with specific evidence]
Domain expertise depth: [where you are genuinely strong]
Career objective for the next two to three years: 
[be specific about what advancement looks like for you]

The six roles I am evaluating:
1. AI output evaluator
2. AI workflow architect
3. AI communications specialist
4. AI ethics and governance professional
5. AI training data specialist
6. AI-augmented domain expert

For each role, please assess:
1. How accessible is this role to me given 
   my current profile, on a scale of 
   near-term, medium-term, or not currently relevant
2. Where the fit between my existing strengths 
   and the role's requirements is strongest
3. The single most significant gap between 
   my current profile and a credible claim 
   to this role

Then recommend one primary role to target 
in the next ninety days with a specific 
rationale grounded in my profile, not 
in which role sounds most appealing.

Also identify the role I am most likely 
to choose for the wrong reason, and why.

The final instruction, to identify the role most likely to be chosen for the wrong reason, is the one that makes this assessment honest rather than confirmatory. Most professionals gravitate toward the role that sounds most impressive or most aligned with their self-image rather than the one most accessible from their current position. The assessment is only useful if it corrects for that bias rather than reflecting it.

Prompt 2: The honest gap analysis

With a target role identified, the next step is understanding precisely what stands between your current position and a credible claim to that role. Not a general sense of the gap. A specific, prioritised inventory of it.

You are helping me conduct a precise gap analysis 
between my current professional profile and 
the specific role I am targeting.

My current profile: [paste from Prompt 1]

My target role: [from Prompt 1 recommendation]

The specific requirements of that role as I 
understand them from the role mapping: 
[paste relevant description from Issue #41]

Please identify:

1. The capability gaps between my current 
   profile and the role requirements, 
   listed in order of their significance 
   to someone hiring for this role today
2. For each gap, assess whether it is 
   closeable in ninety days with focused effort, 
   closeable over a longer period, 
   or structural in a way that requires 
   a different approach
3. The single gap whose closure would most 
   change how a hiring manager or senior 
   colleague evaluates my candidacy for 
   this role
4. The gap I am most likely to underestimate 
   because it does not feel like a gap 
   from the inside, with your reasoning

Be precise. A gap analysis that identifies 
general areas for improvement is not useful. 
One that identifies the specific capability 
whose absence is most visible to the people 
evaluating for this role is.

Point four, the gap most likely to be underestimated from the inside, is the one most professionals find most uncomfortable and most valuable. The gaps that feel like gaps are already being addressed or avoided consciously. The gaps that do not feel like gaps are the ones producing the largest difference between self-assessment and external perception, which is where the most significant development opportunity usually lives.

Prompt 3: The ninety-day objective

With the primary gap identified, the next step is translating it into a ninety-day objective that is specific enough to be measurable and achievable enough to be credible given your actual constraints.

You are helping me set a ninety-day development 
objective that is specific, measurable, and 
grounded in what is actually achievable with 
the time and resources I have available.

My target role: [from Prompt 1]
My primary gap: [from Prompt 2]
My realistic weekly development time: 
[be honest, not aspirational]
My professional context constraints: 
[travel, high-demand periods, competing priorities 
you know are coming in the next ninety days]

Please:

1. Propose a ninety-day objective for closing 
   or significantly reducing my primary gap, 
   stated specifically enough that I will be 
   able to say unambiguously at day ninety 
   whether I achieved it
2. Break it into three thirty-day milestones, 
   each building on the previous one and each 
   assessable with the same unambiguous standard
3. Identify the most likely reason this objective 
   will not be achieved, based on what I have 
   told you about my constraints
4. Propose a modified version that accounts 
   for that failure mode, one that is still 
   meaningful but more robust to the specific 
   risk you have identified
5. Tell me what achieving this objective will 
   specifically demonstrate to the people 
   evaluating me for the target role

The objective that requires perfect conditions 
to achieve is not a plan. It is a wish. 
Build me a plan.

Point five, what achieving the objective will specifically demonstrate, is the connection between the development investment and the career return that makes the investment worth making. Development that is not legible to the people who make career decisions produces capability without career advancement. Understanding in advance what the milestone will demonstrate to the relevant audience shapes both the objective and how the work toward it is documented and shared.

Prompt 4: The weekly practice design

A ninety-day objective is achieved through weekly practice, not through periodic bursts of effort. The design of the practice matters more than the ambition of the objective, because a practice that fits your actual life compounds while one that requires ideal conditions does not.

You are helping me design a weekly practice 
that will compound toward my ninety-day 
objective through consistent, structured effort.

My ninety-day objective and milestones: 
[from Prompt 3]

My realistic weekly development time: 
[from Prompt 3]

My working week structure: 
[describe when you have focused time, 
when you are in meetings, what your 
energy levels are like at different 
points in the week]

Please design a weekly practice that:

1. Fits within the time I have actually available, 
   not the time I would like to have
2. Is structured around application to real work 
   rather than exercises disconnected from 
   my actual professional context
3. Includes a deliberate practice component: 
   the part where I am working at the edge 
   of my current capability rather than 
   doing what I already do well
4. Includes a reflection component of no more 
   than fifteen minutes, structured around 
   three questions: what worked, what did not, 
   and what I will do differently
5. Is attached to a specific existing routine 
   in my week so it does not require a 
   separate decision to begin

Make the practice simple enough that I will 
actually do it on a week when everything 
else is demanding. Complexity is the enemy 
of consistency and consistency is what 
produces compound returns.

Point five, attaching the practice to an existing routine, is the behaviour design element with the strongest research support for sustained follow-through. A practice that requires a separate decision to initiate is subject to the friction of that decision every week. One attached to something that already happens reliably inherits the existing routine's momentum and requires no additional activation energy.

Prompt 5: The thirty-day milestone validator

This prompt is not run now. It is run at day thirty, day sixty, and day ninety. Including it in the plan now ensures it is available when needed rather than constructed in the moment of review when objectivity is harder.

You are helping me conduct an honest 
milestone review at day [30 / 60 / 90] 
of my ninety-day development plan.

My original objective and this milestone's 
specific target: [paste from Prompt 3]

What I actually did in the past thirty days: 
[describe honestly, including weeks where 
the practice did not happen and why]

The output or evidence of progress I have 
produced in this period: [describe specifically]

Please assess:

1. Progress against the milestone target: 
   achieved, partially achieved, or not achieved, 
   with the specific evidence for that assessment
2. The most important thing I learned about 
   my capability development in this period 
   that I did not know at the start of it
3. Whether the original plan's assumptions 
   about my available time and the practice 
   design are holding up or need revision
4. One specific adjustment to the practice 
   for the next thirty days based on what 
   this period revealed
5. Confidence level in achieving the ninety-day 
   objective from here, and what would 
   need to be true for that to change

Be honest. A milestone review that confirms 
everything is on track when it is not produces 
a false sense of progress that makes the 
day ninety assessment more painful than 
it needed to be.

The instruction to be honest rather than confirming what is on track is the one that makes milestone reviews useful rather than ceremonial. Most self-assessments drift toward confirming that the plan is working because abandoning the plan feels like failure. The prompt is designed to make honest assessment feel like information rather than verdict.

Prompt 6: The visibility plan

Development that is invisible to the people who make career decisions produces less career return than equivalent development that is visible to them. Building visibility into the plan is not self-promotion. It is the mechanism by which the investment produces the return it is designed to produce.

You are helping me build a visibility plan 
that makes my ninety-day development visible 
to the people whose assessment of my capabilities 
affects my career trajectory.

My development objective and milestones: 
[from Prompt 3]

The people whose assessment matters most 
and their current awareness of my development: 
[describe each person and their current 
level of awareness honestly]

Please:

1. Identify the most natural point in my 
   ninety-day plan where the development 
   produces an output worth sharing, 
   one that demonstrates capability 
   rather than just announcing effort
2. Propose one specific visibility action 
   for each thirty-day milestone, grounded 
   in the actual output that milestone produces
3. Identify the audience member whose awareness 
   of my development is most important and 
   propose how to ensure that awareness exists 
   by day ninety
4. Identify the visibility action I am most 
   likely to avoid because it feels like 
   self-promotion, and the cost of that avoidance
5. Write the one-sentence description of my 
   development focus that I could use in any 
   professional conversation without overclaiming 
   or underclaiming

The visibility plan should be an output of 
the development, not a performance of it. 
The people you most want to impress are 
the ones most likely to notice the difference.

Prompt 7: The obstacle protocol

Every sustained development effort reaches a moment when the investment feels disproportionate to the visible return. Having a decision framework for that moment, built when motivation is high, produces a better decision than the one made when motivation is low.

I am going to describe three scenarios that 
commonly derail development plans at different 
stages. For each one, give me a specific protocol 
for responding that takes less than fifteen minutes 
to execute and does not require starting over.

Scenario 1: I missed the weekly practice for 
two consecutive weeks because of a high-demand 
work period and the habit has broken.

Scenario 2: I am completing the practice but 
my outputs are not improving at the rate I 
expected and I am questioning whether the 
approach is working.

Scenario 3: Something significant has changed 
in my professional context and the target role 
or the primary gap from the original plan 
may no longer be the most relevant focus.

For each scenario, give me a decision tree: 
the two or three questions to ask and 
the specific action each answer leads to.

The protocol should distinguish between 
plans worth adjusting and plans worth stopping. 
Both are valid outcomes. Continuing a plan 
that should be stopped is not persistence. 
It is sunk cost thinking.

The final instruction, that continuing a plan that should be stopped is sunk cost thinking rather than persistence, is the permission structure that makes the obstacle protocol useful rather than just motivational. Development plans worth stopping exist. The professionals who stop them cleanly and redirect have better outcomes than those who continue them past the point of relevance because abandonment feels like failure.

Prompt 8: The accountability structure

You are helping me build an accountability 
structure for my ninety-day development plan 
that is robust to the pressures that derail 
most development plans.

My plan summary: [objective, milestones, 
weekly practice from above prompts]

My specific risk factors for non-completion: 
[be honest about past patterns, upcoming 
high-demand periods, and the competing 
priorities most likely to crowd this out]

Please:

1. Propose a specific accountability mechanism 
   for each thirty-day milestone: who will I 
   tell, how will I document it, and what 
   will I do if I miss it
2. Design a format for weekly documentation 
   that takes under five minutes to complete 
   and produces a record useful for the 
   thirty-day milestone review
3. Identify the moment in the plan where 
   I am most likely to consider abandoning 
   it and propose a specific protocol 
   for that moment
4. Identify what success looks like at 
   day ninety in terms I can assess 
   without anyone else's validation: 
   the internal standard that tells me 
   the plan worked regardless of whether 
   external recognition has yet followed

Accountability structures that depend on 
external validation for their motivating 
force are fragile. The most robust ones 
are grounded in internal standards the 
professional genuinely cares about.

Prompt 9: The week one launcher

You are helping me design the first week 
of my development plan in enough detail 
that I can begin without any further 
planning decisions.

My plan: [summary of objective, milestones, 
weekly practice, and existing routine trigger]

Please give me a day-by-day schedule for 
week one that:

1. Starts on the first working day 
   after I run this prompt
2. Includes every specific action required 
   to begin the practice I have designed
3. Takes no more than the time I have 
   committed to each day
4. Ends with a five-minute reflection 
   that tells me whether week one is on track

Make the schedule specific enough that 
I do not need to make any decisions 
to follow it. Every decision made now 
is one that does not have to be made 
under the pressure of an actual working week.

Prompt 10: The day ninety closer

Design the day ninety review I will run 
at the end of this plan.

The review should:

1. Assess the objective honestly: achieved, 
   partially achieved, or not achieved, 
   with the specific evidence
2. Identify the most important thing I learned 
   about my capability development that I 
   did not know at the start
3. Assess whether the target role is still 
   the right one to continue developing toward, 
   or whether what I learned in ninety days 
   points toward a different direction
4. Produce the input for the next ninety-day 
   plan: where my current position sits relative 
   to where I was targeting, and what the 
   most important next step is from here
5. Identify the one thing I would do differently 
   if I were starting this plan again with 
   what I now know

The day ninety closer is not the end of 
the process. It is the baseline assessment 
for the next cycle. Design it accordingly.

The forty minutes

Ten prompts. Forty minutes. Run in sequence, each one building on the outputs of the previous ones, they produce a plan with the four properties the research on behaviour change identifies as predictive of sustained follow-through: specificity of the initial commitment, immediate connection between the plan and existing daily behaviour, an explicit mechanism for tracking progress, and a protocol for adjusting when reality diverges from the plan's assumptions.

The plan will not be perfect. No plan built in forty minutes is. What it will be is honest, specific, and structured in a way that makes the gap between intention and action smaller than it is for most development plans, because it was built to close that gap rather than to describe the destination without addressing the distance.

2026 is one week away. The professionals who enter it with a plan like this are in a different position from those who enter it with good intentions and a list of aspirations. The tools are the same for both. The structure is not.

The structure is what compounds.

Monday, December 29, we are looking at the job posting data from the final weeks of 2025 and what it reveals about where the market is actually heading in the first quarter of 2026. Annual forecasts tell you what organisations said they would do. Job posting data tells you what they are doing. The gap between those two things is always instructive.

It is particularly instructive this year.

— The Artificial Idea team

Keep Reading