documentation

Convert feature plans into user stories, Jira CSV, and executive briefs.

1|Updated May 18, 2026
One-click install
npx skills add https://github.com/linenoize/topia --skill documentation-linenoize
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation
Source: https://github.com/linenoize/topia/tree/main/skills/documentation
Command: npx skills add https://github.com/linenoize/topia --skill documentation-linenoize

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns technical plans into clear, leadership-ready documentation so stakeholders can approve work without reading implementation details. It reduces the manual effort of writing stories, summaries, and importable tickets from planning artifacts.

Core Features & Use Cases

  • User Story Generation: Converts phase tasks into Agile user stories with testable acceptance criteria.
  • Jira CSV Export: Produces RFC-4180 compliant ticket files ready for Jira import.
  • Leadership Briefing: Creates an executive summary, timeline, and risk overview for stakeholder review.
  • Use Case: After planning a new feature, use this Skill to produce a polished package that engineering, product, and leadership can all review and approve.

Quick Start

Use the documentation skill to turn the active feature plan into user stories, a Jira-ready CSV, and a leadership brief.

Frequently Asked Questions about documentation

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

FAQPage Schema
How do I generate user stories from a feature plan?

Generating user stories from a feature plan converts phase tasks into Agile stories with testable acceptance criteria. This Skill processes your requirements.md and plan.md to automatically produce these stories alongside leadership briefs.

How do I generate Jira tickets from markdown planning files?

Generating Jira tickets from markdown planning files produces RFC-4180 compliant CSV exports ready for direct import. This Skill reads your plan.md and requirements.md to output importable ticket files under the .topia/features/<name>/ directory.

What is the best way to create a leadership brief from technical feature plans?

Creating a leadership brief from technical feature plans involves summarizing timelines, risks, and executive overviews for stakeholder approval. This Skill extracts high-level details from your planning artifacts to generate a polished leadership review package.

Do I need an adversary report to generate stakeholder-ready documentation?

An adversary report is optional for generating stakeholder-ready documentation. This Skill requires requirements.md and plan.md to function, but will also incorporate an optional adversary-report.md if present in the active feature folder.

Can I use this documentation Skill without any external dependencies?

You can use this documentation Skill without external dependencies because it operates entirely on local markdown files. It processes requirements.md and plan.md to write CSV and markdown artifacts directly into your feature folder.

Why does my Jira CSV import fail when generating tickets from feature plans?

Jira CSV imports fail when files lack RFC-4180 compliance, causing misaligned columns or formatting errors. This Skill prevents import failures by generating strictly RFC-4180 compliant CSV ticket files from your feature plans.