Srnnkls Tropos
Tropos is a Claude Code plugin for the Validate phase that provides spec-driven workflow plugins with TDD, review, and implementer agents in a four-plugin pipeline.
by srnnkls · github.com/srnnkls/tropos
Register Tropos spec-driven workflow plugins so Claude Code runs specs, TDD, review, and implementer agents as a chained delivery pipeline.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install srnnkls-tropos@srnnkls/troposBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:srnnkls/tropos") and the paste-ready config with skillselion.get_install_config("plugin:srnnkls/tropos").
What it does
Tropos by srnnkls is a Claude Code plugin marketplace built for spec-driven development. Solo builders install it when they want written specs, test-driven execution, and separate reviewer or tester agents instead of one-shot code generation. The four plugins combine commands, skills, rules, and specialized agents so work flows from spec definition through implementation and quality review. That makes Tropos a strong fit during validate and ship: you nail scope and acceptance first, then let dispatch and pipeline plugins enforce consistency. It is intermediate complexity because you must maintain specs and respect the workflow order. On Skillselion it appears as a multi-phase workflow marketplace—register Tropos in Claude Code, then invoke the spec and TDD-oriented plugins before leaning on implementer and reviewer roles for build and review work.
Highlights
- Four-plugin marketplace oriented around spec-driven development and slash commands
- Pipeline roles include implementer, reviewer, tester, and quality-focused agents
- Explicit TDD, review, and dispatch keywords for gated execution
- Workflow bundle—not a lone formatter; expects spec → implement → review handoffs
- Pairs rules, skills, and commands for Loqui-style agent orchestration
Why builders use it
Agents that skip written specs and reviews produce inconsistent code and make solo builders redo work that never matched acceptance criteria.
After registering Tropos, you run a spec-first slash-command pipeline where implementer, reviewer, and tester plugins enforce scope, TDD, and quality before merge.
At a glance
- Type - Plugin in Productivity.
- Adoption - 0 installs, 0 stars, 0 votes.
FAQ
Who is srnnkls-tropos for?
It is for Claude Code users who practice spec-driven development and want separate implementer, reviewer, and tester plugins wired through commands and rules.
When should I use srnnkls-tropos?
Use it when defining scope and specs during validate, and keep using it through build and ship whenever you need TDD, dispatch, and structured reviews.
How do I add srnnkls-tropos to my agent?
Install the Tropos marketplace from srnnkls/tropos in Claude Code, then enable the spec, implementer, reviewer, and tester plugins you need for your pipeline.
Comments
Share how you use srnnkls-tropos, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.