Have you ever wanted to install the architecture of a product the way you install an app?
Not just a diagram, but the whole system architecture blueprint:
- services and dependencies
- teams and ownership
- goals → initiatives → work packages
- a 3-year planning horizon for product managers
- plus a “prompt pack” so you can remix it
That’s what I’ve been building as a hobby project: SMT (Software Management & Planning Tool).
And this week I shipped something I’m genuinely excited about:
The Community Blueprints Marketplace (with social features)
You can now publish blueprint packages publicly, and the community can:
- browse and install them
- star them
- comment / discuss them
- see what’s trending (social proof + discovery loops)
Think: Figma Community / Steam Workshop, but for product architecture + product/team organization.
What’s a “Blueprint” in SMT?
A blueprint is a portable package (JSON) that contains:
- a manifest (title, summary, tags, trust label, etc.)
- a prompt pack (seed + variants like MVP/Scale)
- a full system snapshot (teams, services, goals, initiatives, work packages)
The goal is learning through interaction:
- install a blueprint
- explore its org + architecture + roadmap in the app
- remix it into your constraints
- publish your remix back to the marketplace
Why I’m doing this
Most “reference architectures” online are:
- static
- divorced from org/team realities
- not easily remixable
- missing the roadmap/execution story
SMT tries to make “how a product might actually run” tangible:
- architecture + org design + planning are all connected
- you can poke at it, not just read it
SMT makes it possible for you to inspect any type of tech platform. Think LeetCode interview preps but for system design, architecture, team topologies, product roadmaps and software delivery planning.
Local-first by default (privacy + zero friction)
SMT is intentionally local-first:
- it runs as a static app in the browser
- your systems stay in your browser unless you explicitly publish a blueprint package
The cloud marketplace is optional and only powers:
- public publishing
- discovery
- stars/comments
No “workspace sync” SaaS lock-in.
How the social marketplace works (simple + cost-free)
To keep this sustainable on the free tier, the backend is:
- Cloudflare Workers + D1 (SQLite)
- token-normalized search (no paid search / no vector DB)
- GitHub OAuth for identity (scope:
read:useronly)
Important security bit:
- public publishing does secret scanning (manifest + full system payload) and blocks likely API keys/tokens.
Try it (and please break it, it's a WIP hobby project)
1) Open the app
2) Explore the “Community Blueprints” view
- browse the curated catalog
- click Preview on anything that looks interesting
- install an Available blueprint and inspect it across:
- System Architecture Overviews
- Org Design
- Roadmap & Backlog Management
- Year Plan / Detailed Planning
3) Publish + socials
- in the publish flow, use Publish Publicly
- then open Preview on your published blueprint:
- Star/Unstar it
- Post a comment
- sanity check that it’s discoverable via search
If anything fails, I want to know. Use the Feedback feature to log issues.
What I’d love feedback on (high signal)
- Does the blueprint concept actually help you understand a product faster?
- Are the “prompt packs” useful, or just noise?
- What should “trending” mean here: stars, downloads, recency, or something else?
- What social features would make this fun without turning it into a moderation nightmare?
If you want to contribute
This is open source (CC0) and I’m happy to collaborate.
- Repo: https://github.com/khanmjk/altsoftwareplanning
- Issues / PRs welcome: docs, UX polish, seed blueprints, moderation workflows, “remix lineage”, collections, reputation, etc.
Roadmap ideas (if the community likes this)
- Remix lineage: “Forked from…” + remixes graph
- Lightweight contributor reputation (badges, trust tiers)
- Reporting/flagging + moderation queue
- Curated collections (“Backends 101”, “B2B SaaS starters”)
If any part of this sparks your curiosity, I’d love for you to try it for 5 minutes and tell me what confused you, what felt magical, and what felt pointless.
Drop a comment here, or open an issue on GitHub.
