What the SKILL.md actually says
A skill is only as good as its instructions, so we simply describe them here. After the frontmatter with the triggers and the target audience, the file opens with a role description in four short sentences: you are an experienced strategist who builds OGSM plans, you make complex direction concrete and executable on one A4, no vague missions or buzzwords but sharp goals, hard numbers and clear actions. Then comes the theory in brief, and then the core: a working method of seven fixed steps. Version 1.0.0, MIT licence.
The most important rule sits above the steps and sets the whole tone of the conversation: work out the OGSM step by step, only propose a next step once the previous one is sharp, and no eight ideas at once but one proposal with reasoning, then ask. So you do not get a waterfall of options you have to pick from yourself. For the Objective the skill proposes one, explains why that wording, and asks whether it is right. For the Goals it backs up every proposal with the assumption underneath, and explicitly asks whether you want to adjust anything. That way it stays your plan, with the skill as referee.
The steps themselves: first the context, with four questions about the company or team, the period, the current situation and any existing vision or mission. If you do not have time for an extensive intake, the file literally says the skill works with what is there and makes assumptions explicit.
Then the Objective, with good and bad examples in the file itself. Then three to five Goals, each specific, measurable, time-bound, relevant and challenging but realistic. Then the Strategies, with the requirement that every Strategy is explicitly linked to the Goals it supports, and the rule that a Strategy is also about what you do not do. Then the Measures: for each Strategy one to three KPIs and three to five actions with an owner and a deadline.
Step six is the sanity check, and it is stricter than you would expect from a fill-in helper. Five check questions: does it fit on one A4, and if not, cut it, three strong Strategies rather than five weak ones. Does everything connect: does every Goal touch the Objective, does every Strategy touch at least one Goal, does every Measure prove a Strategy. Is there focus, because an OGSM that wants everything achieves nothing, and what have you explicitly cut? Are the numbers ambitious but achievable?
And the last one, the best of the five: does everyone know what to do on Monday? If not, the actions are still too abstract. Only after that comes step seven, the fixed delivery format you saw in FIG.02, including the block on what you deliberately do not do.
The file closes with a list of five things that may never appear in it, worked out below in Section 04, a source list of three entries, and a closing note on rhythm: plan a review every quarter, because the Objective rarely changes, Strategies sometimes and Measures often. More on that below.