jm-adk

Discover, evaluate, and install agent skills from the open ecosystem (skills.sh, GitHub, local plugins). Searches across Skills CLI, skills.sh leaderboard, and local plugin catalogs to recommend the best match. Trigger: find a skill, how do I do X, is there a skill for, can you do X, extend capabilities, search skills, install skill, discover skill, skill marketplace, skills.sh.

Automatically fixes mechanical issues found during plugin validation, including JSON formatting, missing shebangs, file permissions, hook types, frontmatter gaps, and settings.json defaults. ALWAYS asks for confirmation before modifying any files. Trigger: fix issues, auto-fix, fix common problems, repair plugin.

Maps business processes, data flows, and integration points into visual sequence diagrams and dependency graphs. Trigger: "map the flow", "show me how data moves", "integration diagram".

Systematic scan across 10 friction categories affecting development velocity. Trigger: "detect friction", "what's slowing us down", "friction analysis", "velocity blockers".

Produces structured functional specifications including use cases, business rules, and complexity/risk matrices. Trigger: "write the spec", "functional requirements", "use case analysis".

Generates a comprehensive QA report in Markdown combining findings from all validation and audit skills, with executive summary, categorized findings, and prioritized recommendations. Trigger: generate QA report, full report, plugin report, qa summary.

Produces a compact executive scorecard grading a plugin across 7 quality dimensions with a letter grade, numeric score, and top 3 priority actions. Trigger: generate scorecard, qa scorecard, plugin grade, executive summary.

Brainstorm individual plugin components (skill, agent, command, hook) for existing or planned plugins. Trigger: ideate component, brainstorm skill, new agent idea, component concept, add skill to plugin.

Generate a structured plugin concept brief from a user idea. Trigger: ideate plugin, brainstorm plugin, plugin concept, new plugin idea, create plugin concept. Researches existing plugins for overlap, proposes movement structure and component counts.

Create or update a CONSTITUTION.md that defines project governance — establishes coding standards, quality gates, TDD policy, review requirements, and non-negotiable development principles with versioned amendment tracking. Use when defining project rules, setting up coding standards, establishing quality gates, configuring TDD requirements, or creating non-negotiable development principles.

Create a feature specification from a natural language description — generates user stories with Given/When/Then scenarios, functional requirements (FR-XXX), success criteria, and a quality checklist. Use when starting a new feature, writing a PRD, defining user stories, capturing acceptance criteria, or documenting requirements for a product idea.

Generate a technical design document from a feature spec — selects frameworks, defines data models, produces API contracts, and creates a dependency-ordered implementation strategy. Use when planning how to build a feature, writing a technical design doc, choosing libraries, defining database schemas, or setting up Tessl tiles for runtime library knowledge.

Generate quality checklists that validate requirements completeness, clarity, and consistency — produces scored checklist items linked to specific spec sections (FR-XXX, SC-XXX). Use when reviewing a spec for gaps, doing a requirements review, verifying PRD quality, auditing user stories and acceptance criteria, or gating before implementation.

Generate Gherkin .feature files from requirements before implementation — produces executable BDD scenarios with traceability tags, computes assertion integrity hashes, and locks acceptance criteria for test-driven development. Use when writing tests first, doing TDD, creating test cases from a spec, locking acceptance criteria, or setting up red-green-refactor with hash-verified assertions.

Generate dependency-ordered task breakdown from plan and specification. Use when breaking features into implementable tasks, planning sprints, or creating work items with parallel markers.

Validate cross-artifact consistency — checks that every spec requirement traces to tasks, plan tech stack matches task file paths, and constitution principles are satisfied across all artifacts. Use when running a consistency check, verifying requirements traceability, detecting conflicts between design docs, or auditing alignment before implementation begins.

Execute the implementation plan by coding each task from tasks.md — writes source files, runs tests, verifies assertion integrity, and validates output against constitutional principles. Use when ready to build the feature, start coding, develop from the task list, or resume a partially completed implementation.

Convert tasks from tasks.md into GitHub Issues with labels and dependencies. Use when exporting work items to GitHub, setting up project boards, or assigning tasks to team members.

Report a bug against an existing feature — creates a structured bugs.md record, generates fix tasks in tasks.md, and optionally imports from or creates GitHub issues. Use when fixing a bug, reporting a defect, importing a GitHub issue into the workflow, or triaging an error without running the full specification process.

Resolve ambiguities in any project artifact — auto-detects the most recent artifact (spec, plan, checklist, testify, tasks, or constitution), asks targeted questions with option tables, and writes answers back into the artifact's Clarifications section. Use when requirements are unclear, a plan has trade-off gaps, checklist thresholds feel wrong, test scenarios are imprecise, task dependencies seem off, or constitution principles are vague.