skills.rest
sean-m-cooper
sean-m-cooperCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

feature-writer

Coordinate a structured interview to produce a Feature document.

11|7|Updated Apr 2, 2026
Search Tags:#backend-api#feature-definition#product-owner#ui-flow#structured-interview#feature-document
One-click install
npx skills add https://github.com/sean-m-cooper/ai_tools --skill feature-writer-sean-m-cooper
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-writer
Source: https://github.com/sean-m-cooper/ai_tools/tree/main/skills/feature-writer
Command: npx skills add https://github.com/sean-m-cooper/ai_tools --skill feature-writer-sean-m-cooper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides product teams to capture complete feature scopes by conducting a structured, conversational interview that yields a formal Feature document, ensuring consistency and clarity across UI, backend, and full-stack initiatives.

Core Features & Use Cases

  • Walks a Product Owner through a modular interview flow that branches by feature type (UI, backend/API, or full-stack) and produces a structured Feature document.
  • Supports planning screen flows, API definitions, and backend capabilities with clearly defined data requirements and acceptance criteria.
  • Use Case: A PO wants to define a new feature (e.g., a new checkout flow) and receive a ready-to-share Feature document with screens, data needs, and integration points.

Quick Start

Initiate the interview by naming the feature and its scope, then answer the prompted questions to generate a complete Feature document.

Frequently Asked Questions about feature-writer

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

FAQPage Schema
How do I define a new feature through a structured interview?▼

To define a feature through a structured interview, you initiate a conversational flow that branches by feature type and collects data on UI screens, backend resources, and cross-cutting concerns to produce a comprehensive Feature document.

Can I document both UI flows and backend APIs in the same feature definition?▼

Yes, you can document both UI flows and backend APIs simultaneously by selecting the full-stack feature type, which gathers requirements for screen flows, API definitions, and backend capabilities within a single structured interview.

What is the best way to plan a checkout flow and generate a feature document?▼

Planning a checkout flow involves conducting a structured interview to map UI screens, define data requirements, and outline integration points, ultimately outputting a ready-to-share Feature document with acceptance criteria.

Does the feature definition process handle non-happy paths and edge cases?▼

Yes, the feature definition process handles non-happy paths by enforcing a step-by-step interview flow that captures cross-cutting concerns and edge cases, ensuring the final Feature document covers complete scope and clarity.

How do I start the feature definition interview for a new product capability?▼

To start the feature definition interview, name the feature and define its scope, then answer the prompted questions regarding UI and backend data requirements to generate the complete feature documentation.

Related Skills

Explore More Product & Management Skills→
dtsongdtsong
1

intake-skill

Transform natural language project descriptions into structured engagement briefs.

Community
Advanced
zig-whatwgzig-whatwg
11

WHATWG Specification Implementation Skill

Translate WHATWG specifications into Zig implementations with numbered spec references.

Official
Advanced
AlterLab-IEUAlterLab-IEU
23

game-accessibility-specialist

Audit game accessibility across motor, visual, auditory, and cognitive domains.

Community
Advanced
jkitchinjkitchin
34

brainstorming

Facilitate structured brainstorming sessions using SCAMPER and Six Thinking Hats.

Community
Advanced