brief

Generate a feature specification README.md from a task title and codebase analysis.

41|6|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/rickywo/Formic --skill brief-rickywo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brief
Source: https://github.com/rickywo/Formic/tree/main/skills/brief
Command: npx skills add https://github.com/rickywo/Formic --skill brief-rickywo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of detailed feature specification documents for new tasks, ensuring clarity and consistency in project planning.

Core Features & Use Cases

  • Feature Specification Generation: Creates a structured README.md outlining a task's overview, goals, capabilities, non-goals, and requirements.
  • Codebase Exploration: Analyzes the project's tech stack and conventions to inform the specification.
  • Use Case: When a new feature request comes in, use this Skill to generate a comprehensive specification document that the development team can use as a clear blueprint.

Quick Start

Use the brief skill to generate a specification for the task 'Implement user authentication'.

Frequently Asked Questions about brief

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

FAQPage Schema
How do I generate a feature specification document for a new task?

To generate a feature specification document, provide a task title and context to create a structured README.md with sections for Overview, Goals, Key Capabilities, Non-Goals, and Requirements.

Can I automatically analyze my codebase to inform project planning specifications?

Yes, codebase analysis informs project planning specifications by scanning the project's tech stack, architectural patterns, and coding conventions to ensure the generated feature document aligns with existing standards.

What should be included in a feature specification README?

A feature specification README should include structured sections for Overview, Goals, Key Capabilities, Non-Goals, and Requirements to provide a clear blueprint for the development team.

How do I create a structured task specification from a feature request?

You create a structured task specification from a feature request by passing the task title and context, which generates a README.md outlining the project's overview, goals, and requirements.

Does generating task specifications require manual configuration of output sections?

No, generating task specifications does not require manual configuration of output sections, as it automatically structures the README.md with predefined sections for goals, capabilities, and non-goals.

What is the best way to document non-goals and requirements for new features?

The best way to document non-goals and requirements for new features is using a structured README.md format that explicitly separates these sections to maintain clarity and consistency in project planning.