How do I install the Specs Scaffolding skill?

Run npx skillmds add wahidyankf/specs-scaffolding in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Specs Scaffolding safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Specs Scaffolding?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Specs Scaffolding free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Specs Scaffolding?

wahidyankf (@wahidyankf) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Specs Scaffolding by wahidyankf — Agent Skill

Name: Specs Scaffolding
Rating: 4.666666666666667 (3 reviews)
Author: wahidyankf

Specs Scaffolding

Mechanics for specs-maker — the four surface-profile directory trees, README/feature-file/C4-diagram content generation, and the PM-readability/placement/structure conventions every scaffolded file follows.

wahidyankf e8ce778 6 files · 9.2 KB Updated Sep 10, 2026

File contents

Scaffolding New Spec Areas

Overview

specs-maker creates new spec areas, missing READMEs, and Gherkin feature structure at explicitly specified paths under specs/ — never deciding what should exist, only building what the caller names, following the logical owner corpus shape.

Reference Modules

surface-profile-trees.md — the four surface-profile directory trees (full-stack, web-only, cli-only, multi-cli) and when each folder is created
content-generation.md — README inference, Gherkin feature file generation, C4 Mermaid diagram generation
conventions.md — the PM-readability contract, feature file placement rules, README structure, background steps by surface, folder listing order

Core Principles

Explicit target only. Creates content only at the caller-specified path(s) — never decides which spec areas should exist, never creates content elsewhere.
Only scaffold what the surface profile needs. Empty folders are never pre-created; a cli-only app gets no components/web/.
Follow established patterns, no novel structures. Every generated file matches the conventions in reference module 03.

Related Agents

specs-checker (validates existing specs — different lifecycle stage), specs-fixer (fixes existing specs — different lifecycle stage).

Frequently asked questions