decision-board
πPlugin2ykwang/agent-skills
Render an interactive HTML board for the user to pick among multiple comparable options side-by-side at once β engineering trade-offs, copy audits, action-item triage, architecture decisions, policy calls. Returns the picks (and optional hold/note flags) as a JSON file the agent can apply.
Part of
2ykwang/agent-skills
Installation
/plugin marketplace add 2ykwang/agent-skills/plugin install decision-board@2ykwang-agent-skillsMore from this repository10
Agent skills including html-visual for generating interactive single-file HTML visualizations (UI mockups, ERDs, flowcharts, data charts) and ralph-loop-template for iteration checklists.
Agent skills including html-visual for generating interactive single-file HTML visualizations (UI mockups, ERDs, flowcharts, data charts) and ralph-loop-template for iteration checklists.
A Ralph Loop template skill for autonomous agent iteration, part of an agent skills collection that includes HTML visualization and interactive single-file generation capabilities.
Skill
Skill
Skill
Skill
Decide how elaborate to build something (simple vs. robust) and return a concrete, PoC-shaped proposal at that level β not over- or under-engineered, but right-sized. Use whenever someone is building something and the investment level is unclear: "quick or proper?", "MVP vs. real product", "is this over-engineering?", "how should I approach X?", "quick script vs. robust system", "how much architecture?", "how much do I build here?". Fires even without "poc" or "right-size" β any time effort and complexity of what to build are being weighed.
Turn code, specs, a PR, or the current conversation into a QA test-case list a non-developer can read and run, exported as CSV, a shareable HTML report, or both. Trigger when the user wants QA test cases, a test plan, a QA checklist, or a test-case CSV/HTML (e.g. "write test cases for this", "make a QA list"). Output uses behavior-and-scenario language, never code symbols like function names or file paths. Not for writing or running automated test code (pytest/jest), code review, or test-strategy docs.
Analyzes git diff and commit history to write PR title and description based on the project's PR template.