skills.rest
minhquan2904
minhquan2904COMMUNITY
Explore all skills by this author →
GitHub

init

Scaffold OpenSpec change directories and generate metadata.yaml and proposal.md artifacts.

Updated Mar 27, 2026
Search Tags:#scaffold#openspec#change-management#initialize#metadata.yaml#proposal.md
One-click install
npx skills add https://github.com/minhquan2904/vibe-check-scam --skill init-minhquan2904
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: init
Source: https://github.com/minhquan2904/vibe-check-scam/tree/main/.agent/skills/init
Command: npx skills add https://github.com/minhquan2904/vibe-check-scam --skill init-minhquan2904

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces manual setup time for a new feature by scaffolding the required change directory and generating the initial artifacts metadata.yaml and proposal.md.

Core Features & Use Cases

  • Scaffold a new change directory in openspec/changes/<name> using the OpenSpec CLI.
  • Generate the initial metadata.yaml and proposal.md artifacts to outline the feature scope.
  • Collect and incorporate context from multiple sources (user description, Confluence pages, documentation files) to form a complete change plan.
  • Validate and ensure artifacts are placed in the correct path with proper metadata for downstream workflows.

Quick Start

Provide a feature description and inputs, then run the OpenSpec CLI to scaffold the change and artifacts.

Frequently Asked Questions about init

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

FAQPage Schema
How do I scaffold a new feature change directory in OpenSpec?▼

This Skill automates scaffolding a new feature change directory in OpenSpec by creating the openspec/changes/<name> path and generating initial metadata.yaml and proposal.md artifacts to outline the feature scope.

What is the best way to initialize feature proposals using Confluence pages and documentation files?▼

To initialize feature proposals using Confluence pages and documentation files, this Skill collects and incorporates context from multiple sources to form a complete, structured change plan with proper metadata.

Can I use this scaffolding process without prior CLI configuration?▼

You can use this scaffolding process without prior complex configuration, as it targets OpenSpec-driven workflows and leverages the OpenSpec CLI directly to generate the required change directory and artifacts.

Does OpenSpec change management enforce specific artifact placement for metadata and proposals?▼

OpenSpec change management enforces artifact placement by validating that metadata.yaml and proposal.md are placed in the correct openspec/changes/<name> path with proper guardrails for downstream workflows.

Why does my feature initialization workflow require both metadata.yaml and proposal.md?▼

Your feature initialization workflow requires both metadata.yaml and proposal.md to ensure proper artifact validation and provide a structured outline of the feature scope for downstream OpenSpec workflows.

Related Skills

Explore More Software Engineering Skills→
testdoubletestdouble
198

plan-a-feature-to-confluence

Plan a feature specification and publish it to Confluence via Atlassian MCP.

Official
Advanced
081595081595

openspec-propose

Generate proposal.md, design.md, and tasks.md for codebase changes via openspec CLI.

Community
Intermediate
fjpulidopfjpulidop
9

openspec-new-change

Scaffold OpenSpec change directories and guide first artifact creation.

Community
Advanced
pabloimrik17pabloimrik17

openspec-ff-change

Automate creation of OpenSpec change artifacts within CLI workflows.

Community
Intermediate