defprod-{{skill-name}}

Provides a starter template for authoring DefProd agent skills with phased workflows.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/defprod1/defprod-skills --skill defprod-skill-name-defprod1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: defprod-{{skill-name}}
Source: https://github.com/defprod1/defprod-skills/tree/main/contrib/TEMPLATE
Command: npx skills add https://github.com/defprod1/defprod-skills --skill defprod-skill-name-defprod1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a new DefProd agent skill from scratch requires knowing the expected SKILL.md frontmatter format, the phased workflow structure, and cross-agent compatibility conventions. This template gives contributors a ready-made skeleton so new skills follow the same structure as official DefProd skills. ## Core Features & Use Cases - Frontmatter scaffold: Pre-filled YAML frontmatter with name, description, and allowed-tools entries showing the mcp__<server>__<tool> permission format used by Claude Code. - Phased workflow structure: Numbered phases (Discovery, custom phases, Summary) with guidance comments on confirmation gates, action phases, and analysis phases. - Config documentation pattern: A table section for documenting optional keys from .defprod/defprod.json that the skill consumes. - Use Case: A contributor wants to publish a community skill for the DefProd ecosystem. They copy this template, replace the {{placeholders}} with their skill's logic, and produce a SKILL.md that installs and behaves consistently with official skills. ## Quick Start Copy the contrib/TEMPLATE directory, rename it to your skill name, and fill in every {{placeholder}} in SKILL.md with your skill's workflow and rules.

Frequently Asked Questions about defprod-{{skill-name}}

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

FAQPage Schema
How do I create a new DefProd agent skill?▼

Copy the contrib/TEMPLATE directory, rename it, and replace every {{placeholder}} in SKILL.md with your skill's name, description, workflow phases, and rules. The template enforces the same structure used by official DefProd skills.

What frontmatter fields does a SKILL.md file need?▼

A SKILL.md requires name and description in YAML frontmatter for discovery. The template also includes allowed-tools, which Claude Code uses for tool permissions while other agents like Cursor and OpenCode ignore it.

Does this skill template work with Cursor and OpenCode?▼

Yes, skills built from this template work with any agent that reads .claude/skills directories, including Claude Code, Cursor, and OpenCode. The body uses logical MCP tool names so any agent can resolve them.

When should a skill include a confirmation gate phase?▼

Add a confirmation gate when the skill writes files, modifies the product definition, or makes decisions the user should review first. Read-only or analysis-only skills can skip it and go straight from discovery to summary.

What is the allowed-tools field used for in SKILL.md?▼

The allowed-tools frontmatter lists tool permissions consumed by Claude Code, using mcp__<server>__<tool> format for MCP tools. Other agents ignore this field, so the skill body should reference logical tool names instead.