agentleFS
GoodRelaxGoodRelax/gr-whiteboard/skills/issue-driven/SKILL.md

issue-driven

Skill1 starsChanged 6 days agoApache-2.0View on GitHub

Run the Issue-Driven Framework (by GoodRelax) with the person. It walks from the background of a matter to the one question worth answering (the Issue), then down through challenges, measures, and tasks to the answer, one step at a time. It works in the chat, and on the local whiteboard of this plugin (server board-control) when the person asks for it or agrees to it. Use when the user types /gr-whiteboard:issue-driven, asks to sort out a matter with the Issue-Driven Framework (Yomon), or when consult-on-board picks it.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. soilSpoon/skills★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the Issue-Driven Framework and the board to find, with the person, the one question worth answering, and to lead them step by step to …

    line 8

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

issue-driven

Use the Issue-Driven Framework and the board to find, with the person, the one question worth answering, and to lead them step by step to its answer.

Talk in the chat first, one step at a time in short bullets. Open the board only when the person asks for it, or when a picture would make it clearer and you ask "Shall we sort this out on the whiteboard?" and they agree; then run it as the skill talk-on-board says. After open_board, start the watch Monitor of talk-on-board (Open step 2, client.js watch) at once, or you miss every Send. Draw the person's words, not your own ideas, and validate them, as consult-on-board says.

The eight steps

StepWhat it holdsIt holds when
BackgroundThe situation as it isFree form
PurposeWhat the work is forA verb phrase
AnalysisFacts sorted, compared, and readFree form; it leads to the Issue
IssueThe one question worth answeringOne question that can be answered, is worth answering, and is essential. Do not go on to Challenge until it is a question
ChallengeWhat to overcome to answer it (strategy)A verb phrase; a strategy to solve the Issue
MeasureHow to overcome each challenge (tactics)A verb phrase; the tactics for its Challenge
TaskThe concrete work of each measureA verb phrase; the concrete work of its Measure
AnswerThe answer to the Issue, reached through the stepsA statement that answers the Issue, or says it is not reached yet and why

The Japanese labels of the steps are in data/labels.json (SKILL_DIR is the folder of this file).

Run

Show the eight steps in one row first. Ask the person step by step: Background, Purpose, Analysis, Issue, Challenge, Measure, Task, Answer. Organize each answer under its heading. Never skip a step.

  • At the start, show the eight steps and say in a few words where you are now (e.g. "step 2 of 8"). Do not promise how many rounds it takes.
  • The row: draw_mermaid with file set to SKILL_DIR/data/flow-ja.mmd for a Japanese speaker, or SKILL_DIR/data/flow-en.mmd (absolute paths). Above it, write the title: the framework name and the subject (e.g. "Issue-Driven Framework Sample Inc. study group").
  • Fill the box of the current step light blue (edit_items, bg blue). Leave the other boxes as they are. Add no other colors.
  • Under the row, write the headings ("# Background", in the person's language) with the person's words as bullets. Write each measure indented under its challenge, and each task under its measure.
  • Estimate the height of each step's area first and leave room between the areas. When added lines overlap the area below, move the lower areas down.
  • When a step pauses, weigh how much the person has said, how complex or hard it is, and what interests them. If a framework would help, pick one or two from consult-on-board's frameworks.json (the table below is a start), each with its purpose and why it fits now. Offer it in one short, inviting sentence with its benefit, e.g. "We have many options now. Shall we sort them on a decision matrix? It makes the priorities easier to set." The person decides. Make at most one offer per pause, and none when the step is already clear. Talk it through in the chat first, draw it only on the board the person has opened or agreed to, and validate it as consult-on-board says:

    StepTools
    Backgroundpest, 3c, 5-forces
    Purposemvv, smart
    Analysisswot, fishbone, as-is-to-be, four-forms
    Issue5-whys, hmw
    Challengelogic-tree, ansoff, mece
    Measureecrs, scamper, decision-matrix, eisenhower
    Taskraci, gantt, kanban
    After the answerkpt, ywt, pdca

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.