skills.rest
JeremyKalmus
JeremyKalmusCOMMUNITY
Explore all skills by this author →
GitHub

ascent-feature-brief

Generate structured feature briefs with YAML frontmatter and Markdown sections.

27|3|Updated Jan 4, 2026
Search Tags:#architecture#documentation#Claude Code#obsidian#handoff#feature#brief
One-click install
npx skills add https://github.com/JeremyKalmus/parade --skill ascent-feature-brief
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ascent-feature-brief
Source: https://github.com/JeremyKalmus/parade/tree/main/ideas/claude-example/skills/ascent-feature-brief
Command: npx skills add https://github.com/JeremyKalmus/parade --skill ascent-feature-brief

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates concise, implementation-focused briefs that accelerate handoffs to Claude Code by documenting the feature concept, scope, and decision context in a reusable template.

Core Features & Use Cases

  • Generates a structured brief with sections for Summary, User Stories, Behavior & Rules, Boundaries, and Implementation Guidance.
  • Produces Obsidian-ready YAML frontmatter and an equally readable markdown body for easy documentation and traceability.
  • Supports reuse across features to maintain consistency when handing off work to AI coding agents.

Quick Start

Provide a feature idea or goal to generate a complete brief. The output will include the YAML frontmatter and a ready-to-use brief body for your project notes.

Frequently Asked Questions about ascent-feature-brief

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

FAQPage Schema
How do I create a feature brief for Claude Code handoffs?▼

Generating a Claude Code handoff brief requires providing a feature idea to produce a structured document containing summary, user stories, behavior rules, boundaries, and implementation guidance sections.

What format does the feature brief output use for Obsidian compatibility?▼

The feature brief output uses Obsidian-compatible YAML frontmatter paired with a readable Markdown body, ensuring easy documentation and traceability within Obsidian project notes.

Can I use this to generate architecture documentation for AI coding agents?▼

Yes, you can generate architecture and feature documentation for AI coding agents by capturing feature intent, scope, and decision context in a reusable template for consistent handoffs.

What sections are included in a structured feature brief for development handoffs?▼

Structured feature briefs include sections for Summary, User Stories, Behavior & Rules, Boundaries, and Implementation Guidance to document execution-ready development handoffs.

Do I need any dependencies to generate Obsidian-ready Markdown briefs?▼

No dependencies are required to generate Obsidian-ready Markdown briefs, as the skill operates independently to produce YAML frontmatter and readable Markdown bodies from feature ideas.

Related Skills

Explore More Software Engineering Skills→
byonk19-svgbyonk19-svg

shape

Conduct a structured discovery interview to produce a design brief.

Community
Advanced
ZhanlinCuiZhanlinCui
178

obsidian-markdown

Create and edit Obsidian Flavored Markdown notes with wikilinks, embeds, callouts, and frontmatter.

Community
Basic
fikriaffikriaf

claude-code

Automate coding tasks like refactoring and code reviews with Claude Code.

Community
Advanced
lagz0nelagz0ne
12

c3-adopt

Automate C3 architecture documentation creation for existing codebases.

Community
Intermediate