spec

Name: spec
Availability: InStock
Author: marunion

Transform unstructured Markdown, chat history, and images into requirements documentation.

Updated Mar 7, 2026

Search Tags:#documentation #software development #specification #requirements #product management #clarification

Ready to run

npx skills add https://github.com/Marunion/ai-factbomb --skill spec-marunion

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/Marunion/ai-factbomb/tree/main/archflow-main/skills/spec
Command: npx skills add https://github.com/Marunion/ai-factbomb --skill spec-marunion

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill transforms unstructured ideas, notes, or chat logs into a structured, professional requirements document, ensuring clarity and completeness for development.

Core Features & Use Cases

Input Flexibility: Accepts Markdown, Notion exports, chat history, or even image attachments.
Iterative Refinement: Guides users through a Q&A process to clarify details and resolve ambiguities.
Structured Output: Generates a comprehensive requirements document with sections for summary, specifications, non-functional requirements, and more.
Use Case: You have a rough idea for a new e-commerce feature discussed in a team chat. Use this Skill to turn that conversation into a formal requirements document that developers can act upon.

Quick Start

Use the spec skill to create a requirements document for a new user authentication feature.

Frequently Asked Questions about spec

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

FAQPage Schema

How do I turn unstructured chat history into a software requirements document?▼

To turn unstructured chat history into a software requirements document, this Skill processes your chat logs through an iterative Q&A process to clarify details and resolve ambiguities, outputting a structured specification file.

What is the best way to write product specifications from rough Markdown notes?▼

The best way to write product specifications from rough Markdown notes is to use an iterative refinement tool that accepts Markdown input, guides you through clarifying questions, and generates a comprehensive requirements document.

Can I generate requirements documentation from image attachments?▼

Yes, you can generate requirements documentation from image attachments. This Skill accepts various input types including images, transforming them into refined requirements documentation for software services.

Does this requirements clarification process support Notion exports?▼

Yes, the requirements clarification process supports Notion exports. It accepts Notion exports alongside Markdown, chat history, and images to guide you through an iterative Q&A process and finalize specifications.

What format are the finalized software specifications output in?▼

Finalized software specifications are output in Markdown format, specifically saved as a spec.md file within a docs/{serviceName}/ directory structure, adhering to specific ID rules for requirement tracking.