build-plugin-scaffold

Generates complete Claude Code plugin directories from architecture plans and spec files.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/JaviMontano/mao-plugin-qa --skill build-plugin-scaffold-javimontano
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: build-plugin-scaffold
Source: https://github.com/JaviMontano/mao-plugin-qa/tree/main/skills/build-plugin-scaffold
Command: npx skills add https://github.com/JaviMontano/mao-plugin-qa --skill build-plugin-scaffold-javimontano

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Manually assembling a Claude Code plugin directory—with plugin.json, settings.json, hooks.json, agent files, command files, CLAUDE.md, README.md, and LICENSE—is repetitive and error-prone. This Skill automates the entire scaffolding process from architecture plans and spec packages, then validates the result. ## Core Features & Use Cases - Full Directory Assembly: Creates the canonical plugin structure (.claude-plugin/, skills/, commands/, agents/, hooks/) with all configuration files populated from real plan data. - Spec-Driven File Generation: Writes agent and command markdown files directly from specification packages, including alias commands with valid alias-of references. - Documentation Generation: Produces CLAUDE.md and README.md from templates with accurate skill and command tables matching files on disk. - Built-in Validation: Runs a validate-structure smoke test after building and reports CRITICAL findings immediately. - Use Case: After finalizing an architecture plan for a new plugin, invoke this Skill to produce a complete, validated plugin directory in one pass instead of hand-creating dozens of files. ## Quick Start Build a plugin scaffold from my architecture plan at plans/my-plugin-plan.md into the directory ~/projects/my-plugin.

Frequently Asked Questions about build-plugin-scaffold

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scaffold a Claude Code plugin directory?▼

Provide an architecture plan path and a target directory. The Skill reads the plan and referenced spec files, creates the standard directory structure, writes all configuration and documentation files, and runs a validation smoke test on the result.

What files does a Claude Code plugin scaffold include?▼

A complete scaffold includes .claude-plugin/plugin.json, settings.json, hooks/hooks.json, agent markdown files, command files with aliases, CLAUDE.md, README.md, and a LICENSE file, plus skills/, commands/, agents/, and hooks/ directories.

Does the scaffold overwrite an existing plugin directory?▼

No, not without consent. If the target directory already exists, the Skill lists its contents and asks for explicit confirmation before overwriting anything, preventing accidental data loss.

What happens if a spec file referenced in the architecture plan is missing?▼

The Skill halts immediately and reports which referenced spec files are absent. It does not proceed with a partial build, avoiding incomplete or inconsistent plugin directories.

Can the scaffold handle a plugin with no hooks or no commands?▼

Yes. With zero hooks it writes hooks.json as an empty hooks object, and with no commands it still creates the empty commands/ directory while omitting the commands section from CLAUDE.md.

What are the limitations of plugin scaffolding?▼

The validation smoke test checks structure only, not content quality. The Skill also cannot initialize git repositories, and it faithfully reproduces any errors present in the upstream architecture plan or specs.