Your senior product & engineering team, in one command.
Type /raftly and an idea becomes a researched, decided, buildable production blueprint. Then Raftly keeps guiding your repository, building the next piece, verifying it against evidence, and telling you honestly whether you're ready to launch.
/plugin marketplace add roszhan2684/raftly
Not a roadmap prompt. Not a code generator.
Code generators write code. Roadmap prompts write plans. Neither remembers why a decision was made, stops you overbuilding, or tells you the truth about launch readiness. Raftly is the organization around the code.
Plans that can actually be built
Capabilities in dependency order, each with a feature spec and a self-contained implementation prompt.
"Done" means verified
Nothing becomes VERIFIED, COMPLETE or PASS without a recorded test, review or measurement. The scripts enforce it.
Remembers why
Decisions, overrides, assumptions, risks and lessons live in your repo, as plain Markdown and YAML you can diff.
The judgment of a senior organization, behind one command
Raftly routes every decision to the right senior role: product strategy, design, architecture, security, SRE and 17 more. It decides what it can, researches what it can't, and asks you only the genuine business questions.
Orient
Reads your repo and its .raftly/ state. Works out the mode: greenfield, build, review, recovery, migration, launch.
Research
Checks what's current and uncertain against primary sources. Anything it couldn't verify is labelled not verified, never invented.
Decide
Routine choices are made silently. Important ones become recorded recommendations. Only business calls come to you, batched into one question.
Record
Every major decision becomes an ADR with options, confidence, consequences and a revisit trigger. Your overrides keep Raftly's original advice.
Design
2–3 genuinely different UI directions (different interaction models, not different colours), with a recommendation, full screen states and accessibility.
Plan
The simplest architecture that meets the actual requirements. Feature specs, a build graph and one prompt per capability.
Build & verify
/raftly build next implements the next unblocked node, runs your tests and records real evidence before anything is marked done.
Launch honestly
/raftly launch runs a production gate fitted to your product. No evidence means no PASS. "Not applicable" is a valid answer.
It refuses to overbuild
Same command, very different products. Raftly decides which production controls apply to your profile, so a calculator is never judged on missing Kubernetes.
SalesLens: B2B AI SaaS
Capabilities in dependency order, not a calendar
Phases come from dependencies, so nothing starts until what it relies on is verified. This is the calculator's real graph.
Each node has a Definition of Done and its own implementation prompt in .raftly/prompts/.
An operating system for building products with Claude
22 senior roles
From Head of Product Strategy to Principal SRE. Each decision is made by the discipline that should own it, and the reply says who decided.
Decision records & overrides
ADRs with confidence, reversibility and revisit triggers. Overrule Raftly and it records your call, the consequences, and moves on without re-arguing.
Evidence graph
Requirement → feature → screen → API → table → test → metric. Ask "why does this exist?" or "which requirements have no tests?".
Production gate
45 launch checks plus the commonly forgotten 20% (password reset, failed payments, restore drills…), each applied only when it fits your product.
Requirement change engine
Change a requirement and Raftly supersedes it with history kept, then shows the impact across features, decisions, data, tests and docs.
Learning firewall
Learns from your project without poisoning itself. "I hate rounded buttons" stays your preference, never a global rule.
Everything lives in your repo
Plain Markdown and YAML you can review, diff and commit. No account, no backend, no lock-in.
- Product, Design, Architecture, Build documents, plus Security, Data, GTM and Compliance-readiness when relevant
- A visual HTML blueprint with the build graph, decision timeline, risks and readiness
- Five product diagrams: architecture, user flow, screen map, data model and the critical-path sequence
- A 12-slide deck with speaker notes, or your host's native deck tool
- Self-contained prompts, one per capability, that any Claude session can run
my-product/
├── docs/
│ ├── PRODUCT.md DESIGN.md ARCHITECTURE.md
│ ├── DIAGRAMS.md # 5 diagrams, Mermaid
│ ├── BUILD.md SECURITY.md DECISIONS.md
│ ├── decisions/ADR-001-client-only.md
│ ├── features/F001-calculation-engine.md
│ ├── prompts/001-calculation-engine.md
│ ├── blueprint.html
│ └── deck.md
└── .raftly/ # working state
├── state.yaml requirements.yaml
├── build-graph.yaml # dependency order
├── evidence.yaml # intent → code → tests
└── gate.yaml # production gate
Two commands. Then /raftly
Raftly installs into Claude Code once and works in every repository you open.
Inside Claude Code, add the marketplace and install the plugin:
# in Claude Code
/plugin marketplace add roszhan2684/raftly
/plugin install raftly@raftly
Then open any project and run:
/raftly I want to build ...
The same thing from your terminal:
claude plugin marketplace add roszhan2684/raftly claude plugin install raftly@raftly
Update later with claude plugin update raftly@raftly.
No plugin system? Copy the self-contained skill folder into your personal skills directory:
git clone https://github.com/roszhan2684/raftly.git mkdir -p ~/.claude/skills cp -R raftly/skills/raftly ~/.claude/skills/raftly
The optional independent review agents only come with the plugin install.
Requires Claude Code and Python 3.9+ (standard library only). If another tool already owns /raftly, use /raftly:raftly.
Two real blueprints, generated by Raftly
Open the HTML blueprints exactly as Raftly renders them from .raftly/ state.
Tally: calculator for mobile and web
Client-only, exact decimal maths, three real design directions, calculator semantics specified, 29 server checks marked not applicable.
Open blueprint →SalesLens: B2B AI sales coaching
Tenancy with row-level security, an AI eval harness gating launch, billing and metering, consent and compliance readiness, and an open pricing decision.
Open blueprint →Questions
Does Raftly send my code or plans anywhere?
No. Raftly has no backend, no account and no telemetry. Everything it writes stays in your repository. Research uses whatever web tools your Claude session already has.
Will it ask me a hundred questions?
No. It decides routine things itself and records important recommendations. It only asks about genuine business decisions such as pricing or target customer, batched into a single round.
Can I use it on an existing, half-built repo?
Yes. Raftly inspects what exists, records it as current, initialises its state without touching your code, and builds a recovery plan. It never starts with a rewrite.
What if I disagree with a recommendation?
Tell it. It records your decision as a founder override, keeps its original recommendation and the consequences, and proceeds consistently with your choice.
Does it certify my product as secure or compliant?
No. Raftly provides engineering readiness analysis and evidence-based guidance. It flags items that need professional review and never claims certification.
Is it free?
Yes. Raftly is open source under the Apache License 2.0. You need Claude Code to run it.
Have an idea? Type /raftly.
Get a researched, decided, buildable blueprint, and a partner that keeps it honest all the way to launch.