spec-driven

Plugin spec-driven from marketplace afonsoft in afonsoft/skills. Commands read from the repo's manifest — 17 days ago.

Skills (27)

• architecture

  Single owner of everything under docs/architecture/ — ADRs, architecture and design documents, and architecture diagrams. Routes each deliverable to the right engine: /mermaid-architecture for Markdown-native diagrams, /drawio-architecture for editable .drawio diagrams, and the optional archify skil

• building-mcp-servers

  Use when building a new MCP server in TypeScript, Python, or C# that exposes tools to LLMs.

• code-review-and-quality

  Use when reviewing code before it merges, whether written by an agent or a human.

• composio-mcp

  Use when the user asks to connect an AI agent to external apps via Composio, or when Composio CLI or MCP setup fails.

• create-agent-harness

  Use when initializing or migrating an AI agent harness in a repository.

• create-issues

  Use when turning approved plans, specs, PRDs, or Epics into trackable GitHub Issues.

• create-readme

  Use when generating or updating a project README.md or CHANGELOG.md.

• design

  Use when designing, redesigning, or improving a frontend interface in Angular, React, or Blazor. Use for landing pages, dashboards, components, forms, and responsive layouts that must work mobile-first and then scale to desktop.

• diagnose

  Use when the user reports a hard bug, unexpected failure, or performance regression that needs root-cause analysis.

• drawio-architecture

  Use when generating or editing draw.io/diagrams.net architecture diagrams via MCP or native XML.

• execute-specs

  Use when the user asks to implement an approved SPEC SDD using test-driven development.

• gap-analysis

  Use when auditing a repository for evidence-backed gaps between code, SPECs, architecture, and documentation — before a release, after a review, or when the user asks what is missing or divergent. Confirmed gaps become Draft SPECs via write-specs, a tracked GitHub Epic via create-issues, and orchest

• improve-codebase-architecture

  Use when the user wants to improve architecture, consolidate tightly-coupled modules, or make a codebase more testable.

• mermaid-architecture

  Use when generating, documenting, or updating architecture diagrams, flowcharts, sequence, ER, class, or state diagrams using Mermaid in docs/architecture/.

• migration-planner

  Use when planning the migration of a legacy system or monolith — analyzes the source codebase (current repo, or a repo URL cloned to a temp dir) and produces an evidence-based Strangler Fig migration plan with per-domain SPECs. Default target is .NET (Blazor WebAssembly, .NET MAUI, ASP.NET Core); ot

• notebooklm-mcp

  Use when the user wants to configure, authenticate, or use Google NotebookLM via the nlm CLI or MCP.

• observability-and-instrumentation

  Use when adding logging, metrics, tracing, or alerting to production code, or when a past incident lacks diagnostic data.

• obsidian

  Use when working with Obsidian vaults, notes, tasks, properties, bases, plugins, or themes.

• orchestrator

  Central entry point of the afonsoft agent harness. Use when starting a new project, resuming an existing one, planning features/Epics/releases, or running any multi-step agent-driven work. Validates and reconciles SPECs (SDD), audits the codebase and harness for gaps (security, architecture, perform

• qa-analyst

  Use when the user asks for QA analysis, test planning, test cases, or root-cause analysis of a defect. Also use for post-merge PR review analysis: auditing recent closed PRs for Devin/GitHub/security bot comments, verifying whether requested corrections were applied, and turning pending fixes into S

• quality-test-implementation

  Use when raising code quality or test coverage across a .NET, Java, or Python repository.

• reverse-engineer

  Use when reverse engineering binaries, firmware, mobile apps, JavaScript/Electron apps, .NET assemblies, network protocols, or malware samples; when decompiling, deobfuscating, unpacking, debugging, or hooking shipped artifacts; when building agent environments (AgentEnv bundles) of a web applicatio

• scaffold-mvp

  Use when starting a new .NET/Blazor/Angular MVP project in an empty repository.

• sonarqube-autofix

  Use when analyzing SonarQube issues and turning them into SPEC SDDs and tracked GitHub Issues for TDD implementation.

• web-design-guidelines

  Use when auditing UI code for interface-guideline compliance (accessibility, forms, animation, images, performance, UX copy) and/or validating a deployed page against Lighthouse 95+ targets. Produces evidence-based findings (file:line + Lighthouse JSON) and turns confirmed pendencies into Draft SPEC

• wordpress-mcp

  Use when exposing a WordPress site to AI agents via MCP, or when WordPress MCP setup fails.

• write-specs

  Use when the user needs to create or refine a feature SPEC SDD before implementation.

Slash commands (27)

• /spec-driven:architecture

  Execute spec-driven skill: architecture

• /spec-driven:building-mcp-servers

  Execute spec-driven skill: building-mcp-servers

• /spec-driven:code-review-and-quality

  Execute spec-driven skill: code-review-and-quality

• /spec-driven:composio-mcp

  Execute spec-driven skill: composio-mcp

• /spec-driven:create-agent-harness

  Execute spec-driven skill: create-agent-harness

• /spec-driven:create-issues

  Execute spec-driven skill: create-issues

• /spec-driven:create-readme

  Execute spec-driven skill: create-readme

• /spec-driven:design

  Execute spec-driven skill: design

• /spec-driven:diagnose

  Execute spec-driven skill: diagnose

• /spec-driven:drawio-architecture

  Execute spec-driven skill: drawio-architecture

• /spec-driven:execute-specs

  Execute spec-driven skill: execute-specs

• /spec-driven:gap-analysis

  Execute spec-driven skill: gap-analysis

• /spec-driven:improve-codebase-architecture

  Execute spec-driven skill: improve-codebase-architecture

• /spec-driven:mermaid-architecture

  Execute spec-driven skill: mermaid-architecture

• /spec-driven:migration-planner

  Execute spec-driven skill: migration-planner

• /spec-driven:notebooklm-mcp

  Execute spec-driven skill: notebooklm-mcp

• /spec-driven:observability-and-instrumentation

  Execute spec-driven skill: observability-and-instrumentation

• /spec-driven:obsidian

  Execute spec-driven skill: obsidian

• /spec-driven:orchestrator

  Execute spec-driven skill: orchestrator

• /spec-driven:qa-analyst

  Execute spec-driven skill: qa-analyst

• /spec-driven:quality-test-implementation

  Execute spec-driven skill: quality-test-implementation

• /spec-driven:scaffold-mvp

  Execute spec-driven skill: scaffold-mvp

• /spec-driven:sonarqube-autofix

  Execute spec-driven skill: sonarqube-autofix

• /spec-driven:spec-driven

  Run the spec-driven pipeline via the orchestrator skill

• /spec-driven:web-design-guidelines

  Execute spec-driven skill: web-design-guidelines

• /spec-driven:wordpress-mcp

  Execute spec-driven skill: wordpress-mcp

• /spec-driven:write-specs

  Execute spec-driven skill: write-specs

MCP servers (8)

• composio

  connects to: https://connect.composio.dev/mcp

• notebooklm-mcp

  runs: notebooklm-mcp

• deepwiki

  connects to: https://mcp.deepwiki.com/mcp

• drawio

  runs: npx -y @drawio/mcp@latest

• wordpress-mcp

  connects to: https://<YOUR_DOMAIN>/wp-json/mcp/mcp-adapter-default-server

• wordpress-ai-engine

  connects to: https://<YOUR_DOMAIN>/wp-json/mcp/v1/http

• wordpress-ultimate

  connects to: https://<YOUR_DOMAIN>/wp-json/mcp-ultimate/v1

• obsidian

  runs: npx mcp-obsidian-cli@latest

Similar plugins