custom-feature-doc

Generate feature documentation files from active Git branch names using a template.

2|1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/assertchris/claude-skills --skill custom-feature-doc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: custom-feature-doc
Source: https://github.com/assertchris/claude-skills/tree/main/custom-feature-doc
Command: npx skills add https://github.com/assertchris/claude-skills --skill custom-feature-doc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of feature documentation files, ensuring consistency and persistence for tracking feature development across multiple sessions.

Core Features & Use Cases

  • Automated File Creation: Generates a new .md file in the features/ directory based on the current Git branch name.
  • Template Integration: Uses a predefined features/template.md to structure the new document.
  • Placeholder Population: Automatically fills in the branch name and default status placeholders.
  • Use Case: When starting work on a new feature branch like feature/user-auth-v2, this Skill creates features/user-auth-v2.md pre-populated with the branch name and a "In Progress" status, ready for detailed documentation.

Quick Start

Use the custom-feature-doc skill to create documentation for the current feature branch.

Frequently Asked Questions about custom-feature-doc

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

FAQPage Schema
How do I generate feature documentation files for a Git feature branch?

To generate feature documentation for a Git branch, this skill extracts the active branch name and creates a new markdown file in the features directory using a predefined template. It automatically populates branch name and default status placeholders for tracking.

What is the best way to structure markdown documentation for new feature branches?

Structuring markdown documentation for feature branches relies on a template file located at features/template.md. The skill applies this template to new documents, ensuring consistent formatting and initial placeholder population for feature tracking across sessions.

How does feature branch documentation handle edge cases like missing branches or existing files?

Feature branch documentation handles edge cases by checking for existing files before creation and managing missing branch scenarios. This ensures a structured approach to feature tracking without overwriting existing markdown documentation.

Do I need a specific Git repository setup to create feature documentation?

You need an active Git repository with a current feature branch and a markdown template at features/template.md. The skill extracts the branch name directly from Git to generate the corresponding documentation file automatically.

Can I use a custom template to populate feature documentation?

Yes, you can use a custom template to populate feature documentation by modifying the features/template.md file. The skill reads this template to structure the new markdown document and fills in initial status and branch information placeholders.