Viserys plugin
Three skills for Claude Code, Cursor and OpenCode: an interview-driven PRD, task slices and a design doc before any code
- 562 ★ on the repository
- Last commit
- Apache-2.0
Minimal access
Why this level
- The skills only write Markdown documents into the project and run nothing over the network
- The Node.js validators and evals are run by hand and have no network dependencies
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/viserysDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The skills only write Markdown documents into the project and run nothing over the network
- The Node.js validators and evals are run by hand and have no network dependencies
This is third-party code. Review the repository files before installing.
What it does
Viserys walks an agent through three steps before any code. The get-prd skill runs a structured interview, challenges the problem itself, extracts user intent, non-functional constraints and core data entities, and saves the result to docs/PRD.md. The get-tasks skill takes an approved PRD and cuts it into vertical slices, each with a dependency order, measurable acceptance criteria and a test-driven verification gate. Plans land in tasks/<name>/plan.md plus per-task files. The third skill, get-design, writes docs/design.md for a web interface: custom design tokens, mobile-first breakpoints and a full set of interactive states. It explicitly rules out the generic look the authors call AI slop. The repository also ships seven specialist subagent personas in agents (strategist, maester, kingsguard, prover, racer, artisan, chronicler), seven shared checklists for security, testing, Core Web Vitals and definition of done, and Node.js structure validators and evals. Claude Code installs it as a plugin, Cursor and Windsurf through npx skills add. Claude Code, Gemini CLI and Antigravity get the slash commands /get-prd, /get-tasks and /get-design. OpenCode gets an adapter with a viserys agent.
Who it is for. Developers and tech leads who do not want an agent to start coding without a spec, a plan and a design, working in Claude Code, Cursor, Windsurf, OpenCode or Gemini CLI.
Good fit when
- A new feature such as multi-tenant authentication is starting and you want a PRD the agent derives from your interview
- The PRD in docs/PRD.md is approved and has to be split into tasks that subagents pick up one by one
- A monitoring dashboard UI is coming up and you need docs/design.md with tokens and states that avoid a template look
- The team wants one shared process for interview, plan, design and checklists in a single repository
Not a fit when
- You need a small edit in one file: an interview and a plan are overkill for it
- The project already has an approved spec and design system and the process is not going to change
- You want the whole pipeline to run unattended: the get-prd interview expects a person to answer
Example request
I want to build an account area with subscription billing. Interview me and write docs/PRD.md, then break it into vertical tasksLimitations
- The README and part of the docs are in Indonesian; persona and command names are in English.
- The authors claim full support and CI testing only for Claude Code. Cursor and Windsurf work through the open agent skills standard, while Antigravity and Gemini CLI are only structurally validated.
- The core is Markdown plus validators, so output quality depends on the model and on your answers during the interview.
How to disable. In Claude Code remove the plugin with claude plugin uninstall viserys. Skills added through npx skills are removed with the same manager, npx skills remove. The generated docs/PRD.md, docs/design.md and tasks folder stay in the project and are deleted by hand.
FAQ
How do I install Viserys in Claude Code?
Clone the repository and run claude plugin validate ., then claude plugin marketplace add ./ and claude plugin install viserys@viserys --scope user. The other route for any agent is npx skills add rizqinrr/viserys-agent, optionally with --skill get-prd for a single skill.
Which files does Viserys create?
get-prd writes docs/PRD.md, get-tasks creates tasks/<name>/plan.md and task-*.md files, and get-design writes docs/design.md. The skills do not touch other project files on their own.
Can I use just one skill?
Yes. npx skills add rizqinrr/viserys-agent --skill get-tasks installs a single skill. The agent picks a skill by the meaning of your request; slash commands are only a direct way to call one.
Which agents does Viserys work with?
Claude Code is fully tested. Cursor and Windsurf connect through npx skills, OpenCode gets a viserys agent, and Gemini CLI and Antigravity have command adapters that are validated structurally.
How is Viserys different from a plain prompt like make a PRD?
The get-prd skill interviews you step by step, challenges the problem and records constraints and data entities in docs/PRD.md, and get-tasks and get-design continue from that file. The output lives in the repository as input for the next steps instead of staying in a chat.
Discussion
No questions or reviews yet.
Related
PluginsTwo skills for Codex and Claude Code: prd keeps a living implementation checklist and review audits designs from the user's side
Eleven skills take an agent from an idea to verified code through a PRD and RFCs kept as files in the repository
A 33-skill plugin with gates: question the request, verify facts against sources, test first, review by a second model
14 skills that find the gaps in a task before the code: interviews, plans, assumption tests and proof that a bug fix works
A skill that interviews you and writes requirements.md, design.md and tasks.md so Claude Code and Cursor work from one plan
Codely team skills that run agent work in phases: a plan in a file or GitHub issues, review after each phase and a clean commit
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Viserys (this card) | no | 562 | |
| AI PRD Workflow | no | 310 | covers only the PRD stage, with no task plan or design document |
| Superpowers | no | 316,679 | a broad set of development practices, whereas Viserys is focused on the PRD, tasks, design chain |
README in short
The README opens with a three-step diagram, then covers three install routes, a table of skills with their outputs and a table of slash commands. Personas, checklists, validators, an agent support matrix and a repository map follow. A showcase site lives in the site folder.