Instructions for tosin2013/mcp-adr-analysis-server, covering mcp adr analysis server - ai coding agent instructions, project overview, critical technical conventions, esm-only module system and typescript configuration.
AI-powered MCP server for analyzing Architectural Decision Records (ADRs). Runs locally from the mcp-adr-analysis-server npm package. Needs 4 environment variables to run.
Skills for AI-assisted project orchestration following best practices for software development lifecycle, architecture documentation, and quality automation.
Instructions for jrjsmrtn/project-orchestration-skills, covering ai-assisted project orchestration skills, project structure, skill file format, skills overview and development conventions.
Conduct SPARK methodology analysis for new project inception. Use at the beginning of a new project, when evaluating significant features, before bootstrap-project to validate viability, or when pivoting an existing project.
Bootstrap a new project at a chosen graduation tier (t0 minimum, t1 decision-tracked, t2 full pattern language) following AI-Assisted Project Orchestration best practices. Use when starting a new software project, promoting an existing project to a higher tier, or converting an existing project for AI-assisted…
Configure two-stage git hooks (pre-commit + pre-push) for quality automation, with either pre-commit or lefthook as the hook manager. Use after bootstrap-project and setup-adrs, when adding quality gates to an existing project, or when standardizing quality automation.
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
Spec-driven agentic engineering as graph engineering: shape (pitch) -> decide (ADR) -> execute (delegated cycle with adversarial review) -> measure -> eval, with /graph to fan work out across a fleet of subagents (diamond / router / verifier / cycle). Dark-launch eval-gated. Distilled from a real practice.
Use this agent to implement ONE approved, closed-scope cycle and open a PR. It is the serialized writer — never run two executors on overlapping files. Context: A pitch has been shaped and approved. user: "Ship the rate-limiter pitch." assistant: "I'll delegate this closed-scope cycle to the executor agent, which will…
Use this agent to turn a measure-gated decision into a data-backed verdict. Runs read-only checks/queries (DB, logs, metrics) and reports a flip/keep/cut verdict with the data. Never writes code or data. Context: A decision is blocked on "do users actually hit this path?" user: "Before we cut the feature, check if…
Use this agent as a general adversarial verifier node in a graph: given ONE finding/claim/answer, try to kill it and return a real/not-real verdict with reasoning. Fan-out safe — run N in parallel (or with distinct lenses) as a gate before a finding is allowed downstream. Read-only. Distinct from reviewer (which…
Runs after a tool call finishes for Edit, Write and MultiEdit tool calls, executing verify-refs.py with --fix and --no-install (2 commands). From GiustoPiedimonte/agentic-engineering-marketplace.
This skill should be used to design or run a task as a graph instead of a linear chain — fan out independent work across a fleet of subagents, verify findings, and converge. Trigger with "run this as a graph", "fan this out", "parallelize this", "orchestrate this with subagents", "audit every X", "sweep the codebase…
Execute an approved pitch/spec as a delegated, closed-scope cycle with verification and adversarial review. Invoke it yourself with /ship — a cycle spawns a writer and opens a PR, so it starts when you say so. Enforces the execution playbook: right-size gate, pre-spawn filter, doc-bundle, PR format, review.
Make a public GitHub repo well-made and honest. /readme audits and elevates a README — deriving the hero, voice, badges, and sections from the PROJECT's own identity (fidelity gate, propose-and-confirm), with free-form targeted edits; /opensource adds the community-health files, an honest CI gate, and the right repo…
This skill should be used to audit OR elevate the README of a public repository. Trigger with "improve the README", "make the readme high quality", "elevate this readme", "audit the readme", "add badges", "is our README good", or before publishing/releasing a repo. Elevate rebuilds a thin/generic README to a polished…
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
11 3d agoA35 tokens
originalApache-2.0
At most 3 mods per repository are shown here — the rest are on their repository pages: