Requirement Solution Design (req-design)

Forces every scheduled requirement through a design pass: two or more options, a decision record, a blast-radius list and acceptance checkpoints written back into the requirement doc.

Docs & OfficeIntermediate★ 544⑂ 41AI score 8/10Last updated: Nov 6, 2026

What it does

Runs the design step before implementation, pulling discussion out of chat/meetings and back into the requirement document.
Requires at least two options (including "change nothing but docs/process"), each with approach, scope of change, cost, main risks and why it was rejected.
Produces a decision record: what was chosen, why, what was dropped, who decided and when, plus assumptions that trigger a re-review if invalidated.
Lists the blast radius — callers, configuration, data migrations, external interfaces, docs, other teams — with a concrete verification for each (a test, a command, an owner sign-off).
Breaks the expected outcome into an acceptance checkpoint table (checkpoint / when / how to verify / pass criteria).
Writes everything back into the doc via lark-cli and records review opinions on the Meegle workflow node.

Who it's for

TPMs, product owners and tech leads on teams using Lark (Feishu) docs plus Meegle.
Organizations that want a repeatable "no implementation without a written decision" habit.
Anyone who wants to lift the decision-record and acceptance-table templates and adapt them to their own tracker.

Example uses

"The payment retry requirement is scheduled — how do we pick an approach?" → generates option A/B/do-nothing comparison plus a draft decision record.
"What else does this change touch?" → a blast-radius list covering calling services, config keys, migrations and public API docs, each with a verification step.
After the design review passes → writes the review opinion to the Meegle review node and inserts checkpoints (review passed / critical-path tests / canary metrics) into section 6 of the doc.

· · · Install guide · · ·

Try it now, no install

Paste this into Claude to use the skill without installing anything.

Read the instructions in this file and follow them to help me:
https://raw.githubusercontent.com/MiniMax-AI/mcode-stack/HEAD/stacks/req-tpm/skills/req-design/SKILL.md

What I want: (describe your task here)

If Claude can't open the link, open it yourself and paste the contents instead.

↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.

Install in the Claude app (no terminal)

Download the ZIP with the button below.
In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.

↓ Download ZIP

Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on AI Skill Mart.
Copy the stacks/req-tpm/skills/req-design folder from the GitHub repo MiniMax-AI/mcode-stack into my ~/.claude/skills/req-design/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/MiniMax-AI/mcode-stack.git && mkdir -p ~/.claude/skills && cp -r mcode-stack/stacks/req-tpm/skills/req-design ~/.claude/skills/

⚠ This is a third-party skill. Check the source repository before installing.

Clone the repository: git clone https://github.com/MiniMax-AI/mcode-stack.git
Create the skills directory: mkdir -p ~/.claude/skills
Copy the skill: cp -r mcode-stack/stacks/req-tpm/skills/req-design ~/.claude/skills/
Also copy templates/meegle-field-mapping.md from the same stack and sop-transition-node.md from the meegle skill so the internal references resolve.
Prerequisites: install and authenticate lark-cli (Lark/Feishu doc access) and the meegle CLI. Without them, replace the command sections with your own tracker's tooling.
Restart Claude Code and ask something like "design the solution for this scheduled requirement" to trigger the skill.

View source on GitHub ↗License: MIT