A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
0 ★ · Jarroslav/agentic-os · read from the repository page · (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score
score 703 · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository Jarroslav/agentic-os;first catalogued 2026-10-09;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
**Turn your repo into a governed multi-agent setup in one interview** — scoped agent contracts, enforcement hooks (not just prompts), and optional SDLC orchestration. Works in Claude Code and Cursor; the SDLC pipeline (**agentic-sdlc**) also runs in Codex. In plain words You install two plugins into your AI coding editor (Claude Code or Cursor). The first, **agentic-os**, sets up guardrails for AI agents in your project: what files they may touch, when they must stop and ask a human, and how their work gets independently reviewed before anything is committed. The second, **agentic-sdlc**, runs a software-delivery pipeline on top of those guardrails: it takes an idea or a ticket and carries it through requirements, a spec, a plan, tested code, and a review-ready pull request. You don't need to be a programmer to benefit — there are role setups for developers, QA, architects, DevOps, business analysts, project/portfolio managers, security engineers, data engineers, and designers, and the non-coding roles work entirely through plain chat phrases. Unfamiliar terms (HITL, gate, preset…) are one-liners in the Glossary. Start here > **Prefer a walk-through?** The **role-based setup guides** > cover the same install for every role preset — pick your role (developer, QA, > BA/PO, architect, DevOps, PM, portfolio, security, data, design) and follow > the checklist, quick or fully guided. **New to this repo?** You do not need to read everything below. Pick a path: | Your goal | Install from marketplace | First command in *your* project | |-----------|--------------------------|----------------------------------| | **Governed agents in my repo** — scoped writes, blind pre-commit review, role presets, stack agents | **agentic-os** + **agentic-sdlc** + **superpowers** (≥ **6.1.0** — enforced by /agentic-init; see plugins/agentic-os/manifest/dependencies.json) | Choose roles: /agentic-init --presets ba-po → /agentic-doctor | | **SDLC pipeline on top** — spec → plan → TDD → QA (/sdlc-guided, /sdlc-auto, …) | Same three plugins (pipeline skills ship in **agentic-sdlc**) | After init: /sdlc-guided or run **sdlc-preflight** | | **QE AI blueprints** — 28 QE methodology blueprints, scaffold an agent framework from one, or set up evals for skills/agents | **agentic-qe** (works alone — no /agentic-init needed; composes with the other two when they are installed) | Ask e.g. *"scaffold the bug-reporting blueprint for Claude Code"* or *"set up evals for my skills"* | **Five-minute flow (any editor):** 1. Install the plugin(s) for your editor (Claude Code or Cursor). 2. Open the **git repo you want to improve** (not this marketplace repo). 3. Run /agentic-init --presets (or /agentic-init for the full role-selection interview). 4. Run /agentic-doctor — expect passed: true in .agentic/agentic-os/doctor.json. 5. git status — review scaffolded files; nothing is committed for you. 6. If you use the SDLC pipeline, run **sdlc-preflight** — expect passed: true in .agentic/agentic-sdlc/doctor.json. **Safe first try:** use the throwaway repo walkthrough before touching a real project. Full install checklist Complete this **before** /agentic-init in the repo you want to equip: | # | Requirement | How to check | |---|-------------|--------------| | 1 | **Claude Code** or **Cursor** | Editor running with plugin support | | 2 | **python3** 3.10 or newer on PATH | python3 --version — enforcement hooks and the installer runtime are Python; the 3.9 bundled with macOS is too old | | 3 | **git** | Target directory is a git repo (git status) | | 4 | **node** on PATH | node --version — checked by **sdlc-preflight** when using **agentic-sdlc** | | 5 | **superpowers** plugin ≥ **6.1.0** | Install superpowers | | 6 | **agentic-os** custom marketplace added | Install for your editor | | 7 | **agentic-os** + **agentic-sdlc** plugins installed | Both cards/skills visible after reload | | 8 | **gh** (optional) | Only for GitHub ticket/MR adapters | **After equip — which doctor?** | Check | When | Output | |-------|------|--------| | /agentic-doctor | After /agentic-init or /agentic-upgrade | .agentic/agentic-os/doctor.json — manifest, hooks, dependencies, scorecard | | **sdlc-preflight** skill | Before /sdlc-guided or other SDLC skills | .agentic/agentic-sdlc/doctor.json — superpowers, node, git | > **Cursor users:** this plugin is **not** in Browse Marketplace → All (curated > public plugins only). You add a **custom marketplace** and install from the > **User** tab — see Cursor install.