What problem does it solve? Creating a new pipeline extension in a monorepo often produces inconsistent directory shapes, untracked empty directories, and READMEs that omit critical details like installed commands, hooks, or install instructions. This Skill enforces sibling-convention consistency and documentation completeness when scaffolding a new extension. ## Core Features & Use Cases - Convention Matching: Surveys existing extensions/*/README.md and extension.yml files so the new tree matches the established monorepo shape instead of inventing a new one. - Git-Trackable Scaffolding: Ensures every directory named in the task's file list exists with a placeholder or real file so nothing is silently absent from version control. - Complete README Authoring: Requires the README to state installed commands and skills, hook declarations (explicitly noting zero hooks when applicable), and the exact install command. - Use Case: When a task asks you to scaffold a new extensions/<name>/ extension with commands, skills, and tests, this Skill guides you to mirror sibling layouts, place files exactly where specified, and verify the final tree against the task's directory list before reporting done. ## Quick Start Scaffold a new pipeline extension named my-extension under the extensions directory, matching the existing sibling layout and writing a complete top-level README.
