spec

Define and iterate 5-item product specifications from user interviews.

1|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/october-academy/agnt --skill spec-october-academy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/october-academy/agnt/tree/main/skills/spec
Command: npx skills add https://github.com/october-academy/agnt --skill spec-october-academy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SPEC 작성과 이터레이션을 통해, 팀이 동일한 목표와 기대를 공유하도록 돕습니다. 인터뷰 인사이트를 바탕으로 제품 스펙을 단단하게 정의하고, 반복적으로 개선합니다.

Core Features & Use Cases

  • 인터뷰 인사이트를 반영한 SPEC 버전 관리: v1에서 시작해 피드백에 따라 이터레이션합니다.
  • 5개 항목의 구조화된 SPEC으로 문제 정의, ICP, 핵심 기능, 수익 모델, MVP 범위를 빠르게 합의할 수 있습니다.
  • MVP 계획 및 기록: 2주 내 MVP 범위를 설정하고 추적합니다.

Quick Start

인터뷰에서 얻은 통찰을 바탕으로 SPEC의 초안을 작성하고 피드백 루프를 시작하세요.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I define product specifications from user interviews for early-stage discovery?

Product specifications from user interviews are defined by structuring insights into a 5-item SPEC: problem, ICP, core features, revenue model, and MVP scope. This workflow ensures cross-functional alignment across design, engineering, and product teams.

What is the best way to structure MVP scope for cross-functional alignment?

The best way to structure MVP scope is using a enforced 5-item SPEC structure covering problem, ICP, core features, revenue model, and MVP scope, which helps design, eng, and product teams quickly agree on product expectations and track the 2-week MVP boundaries.

How do I iterate product specs based on interview feedback?

You iterate product specs by applying versioned iterations starting from a v1 draft. Interview insights are used to refine the problem definition, ICP, core features, revenue model, and MVP scope through repeated feedback loops to solidify the product direction.

What should be included in an early-stage product spec for an MVP?

An early-stage product spec for an MVP should include five structured items: the core problem, the Ideal Customer Profile (ICP), core features, the revenue model, and the defined 2-week MVP scope to ensure team alignment and trackable delivery.

Can I use structured product specifications for cross-functional team alignment?

Yes, structured product specifications enforce a unified 5-item structure that helps design, eng, and product teams share identical goals and expectations. This structured approach enables fast agreement on requirements and MVP scope during product discovery.