Give each stage of product planning a clear job.

A skill is a reusable set of instructions for a task. The five roles described here are part of the published StoriesOnBoard workflow: Product Discovery, Story Map Creator, Gap Finder, Story Refiner, and Navigator. They run in an agent environment; they are not five extra buttons in the StoriesOnBoard toolbar.

MCP supplies access to the live board. The skill explains how to approach the work. Your brief supplies the actual product problem. Keep those three pieces distinct when setting up or debugging the workflow. A detailed instruction cannot compensate for missing access, and a working connection cannot decide which product to build.

Choose a role based on what is uncertain now. Discovery addresses an unclear problem. Creation organizes an agreed direction. A gap review challenges the resulting coverage. Refinement develops selected stories. Navigation helps identify the current stage and the next unresolved decision.

The table is a practical way to plan a handoff. Treat its output checks as review questions for your team, not as a claim that the model can certify completion.

Suppose the starting request is “build a food app.” A creation task could produce hundreds of plausible cards while missing the actual problem. Begin by clarifying who orders, which delivery model applies, and what outcome the first release needs to support. Record what is outside the scope.

Once the team agrees on meal ordering for a first-time customer, move to a backbone and a proposed release. Ask for a preview of goals, steps, and stories before writing them to the board. After creation, inspect the hierarchy and check whether the release still supports the agreed outcome.

A gap review of the example might notice that payment has only a success path. Ask whether a failed payment needs a retry story, a new payment method, an order-state explanation, or a combination. The answer depends on the service's actual rules; finding a gap is not the same as choosing its solution.

After a decision, refine the selected story. Specify what remains in the cart, what the customer sees, and how another attempt begins. Keep unknown payment-provider behavior in an open question until someone verifies it. This produces a smaller, more useful handoff than fully specifying every possible future feature.

Use an agent environment that supports your skill instructions and connect StoriesOnBoard MCP for board operations. Read the linked five-skill walkthrough for the workflow's intent. This page does not provide an installer or claim that a downloadable package is bundled with every host.

Begin with one map and one stage. Tell the agent what it may read, what it should propose, and when you want to review changes. At the handoff, keep the map reference, decisions, exclusions, and unanswered questions together. A new agent or a fresh conversation should be able to identify the next task without recreating the product definition.