skills.rest
aroido
aroidoOFFICIAL
Explore all skills by this author →
WebsiteGitHub

agent-spec-writer

Generate frontend feature specifications from GitHub Issues and planner results.

Updated Apr 22, 2026
Search Tags:#documentation#frontend#specification#technical writing#issue tracking#requirements gathering
One-click install
npx skills add https://github.com/aroido/vibesmith --skill agent-spec-writer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-spec-writer
Source: https://github.com/aroido/vibesmith/tree/main/.codex/skills/agent-spec-writer
Command: npx skills add https://github.com/aroido/vibesmith --skill agent-spec-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of detailed frontend feature specifications by analyzing GitHub Issues and planner outputs, ensuring comprehensive and actionable documentation.

Core Features & Use Cases

  • Issue Analysis: Extracts requirements, user stories, and acceptance criteria from GitHub Issues.
  • Spec Generation: Creates structured frontend specifications based on a defined template, including product context, functional requirements, and technical guidance.
  • Use Case: When a new feature request is logged as a GitHub Issue, this Skill can automatically draft a complete specification document, ready for review by the product and engineering teams.

Quick Start

Use the agent-spec-writer skill to generate a frontend spec for issue number 123.

Frequently Asked Questions about agent-spec-writer

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

FAQPage Schema
How do I generate frontend specifications from GitHub issues automatically?▼

To generate frontend specifications from GitHub issues, this Skill analyzes issue requirements and user stories to produce structured documents covering product context, functional requirements, and technical guidance.

What is the best way to structure frontend feature specifications for engineering teams?▼

Frontend feature specifications should follow a 3-layer format: Product Context, Functional Requirements, and Technical Guidance, ensuring comprehensive and actionable documentation for engineering teams.

Can I use MoSCoW prioritization to define acceptance criteria in technical writing?▼

Yes, you can use MoSCoW prioritization to define clear acceptance criteria in technical writing, ensuring features are categorized by priority while adhering to specific domain terminology and business context.

How do I extract user stories and acceptance criteria from issue tracking data?▼

Extracting user stories and acceptance criteria from issue tracking data involves analyzing GitHub Issues and planner results to identify requirements and draft complete specification documents ready for team review.

Does agent-spec-writer work with planner results to create structured technical documentation?▼

Yes, agent-spec-writer works with planner results and GitHub Issues to create structured technical documentation, analyzing raw requirements to output detailed frontend feature specifications.

What limitations exist when drafting specifications from issue tracking outputs?▼

When drafting specifications from issue tracking outputs, limitations include dependency on the quality of the original issue requirements and the need for manual review to ensure the generated document aligns with business context.

Related Skills

Explore More Software Engineering Skills→
SebastienDegodezSebastienDegodez
8

issue-refinement

Transform raw GitHub issues into structured user stories validated against INVEST criteria.

Community
Advanced
endaomentendaoment

spec-and-plan

Convert free-form feature descriptions into technical specs and tracking issues.

Official
Intermediate
aroidoaroido

spec-writer

Generate frontend feature specifications using a 6-step process and 3-layer template.

Official
Intermediate
posit-devposit-dev
4.2k

positron-issue-creator

Drafts complete GitHub issue drafts for the Positron repository with duplicate checking.

Official
Basic