Strategy Skills

A true two-way Q&A brainstorming experience for your organisation's strategy work. Use when defining the services, deciding what a service contains, shaping how a service is delivered as a business, or setting marketing direction, and you want to think it through properly before committing. Trigger phrases include "brainstorm", "let's think through", "help me work out", "explore options", "what are our options", "ideas for", "open this up". Asks open questions the user answers in their own words, checks evidence and marks unproven claims, presents 2 to 3 visualised options only after the user has described the problem, and ends only when the user is satisfied, at which point the result is locked as trusted. Output is a lean markdown plus a Word-style HTML in the configured brainstorming folder.

Define the organisation's North Star and the goal and milestones under it. The star is the guiding statement plus the one metric (the enduring direction). The goal is that metric reaching a target by a date (the destination). The milestones are the staged checkpoints (the path). The top-down anchor the other skills align to. Use when setting or refining the company's guiding goal, its one metric that matters, its target, or what winning looks like. Trigger phrases include "north star", "north star metric", "NSM", "business goal", "milestones", "target", "guiding vision", "what should we optimise", "one metric that matters", "what does winning look like". Question-led, evidence-checked, writes one North Star file into the configured north-star folder as lean markdown plus brand-styled HTML. Sits above brainstorm, pain-point and wwwh.

Define a single customer pain point in depth, one pain per run, by asking the user questions. For the chosen pain it captures the voice (the configured buyer voices, default Founder, C-Level, Engineer), the pain, the proof, the service(s) it relates to, its importance, and the objections that stop customers coming on board even when they have the pain. Trigger phrases include "pain point", "define this pain", "work this pain", "customer pain", "objections", "why won't they buy", "what is stopping them", "prove the pain". Question-led: the pain comes from the user, proof is confirmed at source where it already exists, and it writes one file per pain into the configured pain-points folder as lean markdown plus brand-styled HTML. Sits between brainstorm and wwwh.

Initialise (or reconfigure) a project to use the Strategy Skills plugin. Run this once at first launch, before any other strategy skill. It asks for the organisation name, the products, where documents should live, the brand colour and the voice rules, then writes .strategy-skills/config.json and creates the output folders. Every other skill reads that config instead of hardcoded names and paths, which is what makes the plugin shareable across organisations. Trigger phrases include "set up strategy skills", "initialise strategy skills", "configure strategy skills", "strategy skills setup", "first launch", "change the config", "rename the organisation", "move the output folders", "change the brand colour". Run it again any time to edit the config.

The team workflow and co-working control center. An application, operated by talking to Claude in this project, that manages the team's tasks, runs the right skill to get each one done, AND routes requests between people, asking someone to review a document, review a session or decision, give input you are missing, validate your thinking, or sign something off. Use to add items, ask what you or someone else has, see what is due or what is next, work the next task by running its skill, remind people, and to ask a colleague for review, input, validation or approval and record what comes back. Trigger phrases include "tasks", "what do I have to do", "what is due", "what is next", "what does <person> have", "work the next task", "add a task", "mark done", "remind", "action items", "workflow", "register", "who owns this", "ask <person> to review", "review this document", "review this decision", "get <person>'s input", "I need input on", "validate my thinking", "approve", "sign off", "what have I been asked to do", "my inbox", "what am I waiting on". The register lives in the configured tasks folder as register.json, the source of truth. It does not need GitHub. It is designed to be read or driven by an external rules engine for reminders.