One-click install
npx skills add https://github.com/pcatattacks/solopreneur-plugin --skill spec-pcatattacks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/pcatattacks/solopreneur-plugin/tree/main/skills/spec
Command: npx skills add https://github.com/pcatattacks/solopreneur-plugin --skill spec-pcatattacks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Draft structured PRDs (Product Requirements Documents) from validated ideas or feature requests to ensure clear scope, alignment, and actionable guidance for engineering, design, and stakeholders.

Core Features & Use Cases

  • Draft a complete PRD with sections: Overview, User Stories, Acceptance Criteria, Release Phases (MVP, P1, P2), Technical Requirements, Non-Functional Requirements, Out of Scope, Open Questions.
  • Validate drafts via parallel subagents (engineer for feasibility, designer for UI/UX) and save the final PRD to .solopreneur/specs/{date}-{slug}.md for traceability.
  • Handle ideas that specify scope, stakeholders, and questions, ensuring the PRD is ready for review or ticketing.

Quick Start

Provide an idea description or discovery brief path, and the skill will draft a structured PRD.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I draft a structured PRD from a validated idea or feature request?

To draft a structured PRD, provide a validated idea description or discovery brief path. The skill generates a complete document with user stories, acceptance criteria, release phases, and technical requirements, saving the output to a local markdown file for traceability.

What sections should a product requirements document include for engineering and design alignment?

A product requirements document should include an Overview, User Stories, Acceptance Criteria, Release Phases (MVP, P1, P2), Technical Requirements, Non-Functional Requirements, Out of Scope, and Open Questions. This structure enforces clear scope and actionable guidance for stakeholders.

How do I validate technical feasibility and UI/UX during PRD creation?

You can validate technical feasibility and UI/UX during PRD creation by running parallel subagents. The skill deploys an engineer subagent for technical validation and a designer subagent for UI/UX checks to ensure the product requirements are sound.

Can I generate user stories and acceptance criteria directly from an idea description?

Yes, you can generate user stories and acceptance criteria directly from an idea description. The skill processes your feature request to automatically draft these sections alongside release phases and non-functional requirements within the final markdown document.

How are completed PRDs saved for future traceability and ticketing?

Completed PRDs are saved for traceability by writing the final markdown file to a local directory path. The output is stored at .solopreneur/specs/{date}-{slug}.md, ensuring the structured documentation is ready for review or ticketing.