Run any Skill in Manus with one click

Get Started

feature-spec-definition

Stars22

Forks4

UpdatedMarch 1, 2026 at 04:02

Generate structured specification documents in docs/plan/<feature>/ from ambiguous requirements.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

vspo-lab

vspo-lab/vspo-portal

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Computer and Information Systems ManagersManagement Occupations·SOC 11-3021

SKILL.md

readonly

name	Feature Spec Definition
description	Generate structured specification documents in docs/plan/<feature>/ from ambiguous requirements.
user_invocable	true

Overview

A skill for defining feature development specifications. Interviews ambiguous requirements and generates specification documents in docs/plan/<feature>/ aligned with Clean Architecture layers.

Execution Steps

Step 1: Requirements Interview

Confirm the following in a single set of questions:

Feature name (English kebab-case, e.g., user-profile)
Purpose and background of the feature (why build it)
Target users and usage scenarios
In Scope / Out of Scope
Affected entities (new or existing changes)
Key use cases (1-5)
API endpoints (expected)
Frontend screen layout (expected)
Open items

Step 2: Specification Document Generation

Based on the answers, create the following files in docs/plan/<feature>/. Refer to the specification file overview in docs/plan/README.md for the items to include in each file.

00_OVERVIEW.md - Feature overview, purpose, scope
01_DOMAIN_MODEL.md - Entity changes, business rules
02_DATA_ACCESS.md - Repository and DB changes
03_USECASE.md - UseCase layer changes
04_API_INTERFACE.md - API endpoint specifications
05_FRONTEND.md - Frontend UI specifications

For backend-only or frontend-only features, omit unnecessary files. Mark undecided parts as TBD.

Step 3: Spec Review Summary

After generation, present the following:

List of generated files
Summary of confirmed items
Open items and next discussion points to resolve
Guidance on reflecting changes to docs/domain/ if needed

Rules

Specifications are consolidated in docs/plan/<feature>/ (do not scatter them elsewhere)
Entity definitions follow Zod Schema First (per docs/web-frontend/typescript.md)
Guide important decisions to also be recorded in docs/domain/decisions.md

Reference Documents

docs/plan/README.md
docs/domain/README.md
docs/backend/server-architecture.md
docs/web-frontend/architecture.md

More from this repository

same repository

frontend-development

vspo-lab/vspo-portal

Next.js 15 Pages Router frontend development. Feature-based + Container/Presenter pattern, MUI v7 + Emotion CSS-in-JS.

2026-03-2022

api-testing

vspo-lab/vspo-portal

Build API client tests with Vitest and MockHandler. Validate OpenAPI contract compliance with table-driven tests and minimal mocks.

2026-03-0122

backend-development

vspo-lab/vspo-portal

Next.js 15 + Cloudflare Workers + @vspo-lab/api client. Result-type error handling, OpenAPI-generated client, feature-based architecture.

2026-03-0122

code-review

vspo-lab/vspo-portal

PR/code review based on architecture rules. Detects violations of UseCase implementation rules, Result type, and JSDoc conventions.

2026-03-0122

commit

vspo-lab/vspo-portal

Create a conventional commit. No Co-Authored-By trailer.

2026-03-0122

design-system

vspo-lab/vspo-portal

Design tokens (OKLch), color palette, typography, UI patterns, accessibility (WCAG 2.2).

2026-03-0122

name	Feature Spec Definition
description	Generate structured specification documents in docs/plan/<feature>/ from ambiguous requirements.
user_invocable	true

Overview

A skill for defining feature development specifications. Interviews ambiguous requirements and generates specification documents in docs/plan/<feature>/ aligned with Clean Architecture layers.

Execution Steps

Step 1: Requirements Interview

Confirm the following in a single set of questions:

Feature name (English kebab-case, e.g., user-profile)
Purpose and background of the feature (why build it)
Target users and usage scenarios
In Scope / Out of Scope
Affected entities (new or existing changes)
Key use cases (1-5)
API endpoints (expected)
Frontend screen layout (expected)
Open items

Step 2: Specification Document Generation

Based on the answers, create the following files in docs/plan/<feature>/. Refer to the specification file overview in docs/plan/README.md for the items to include in each file.

00_OVERVIEW.md - Feature overview, purpose, scope
01_DOMAIN_MODEL.md - Entity changes, business rules
02_DATA_ACCESS.md - Repository and DB changes
03_USECASE.md - UseCase layer changes
04_API_INTERFACE.md - API endpoint specifications
05_FRONTEND.md - Frontend UI specifications

For backend-only or frontend-only features, omit unnecessary files. Mark undecided parts as TBD.

Step 3: Spec Review Summary

After generation, present the following:

List of generated files
Summary of confirmed items
Open items and next discussion points to resolve
Guidance on reflecting changes to docs/domain/ if needed

Rules

Specifications are consolidated in docs/plan/<feature>/ (do not scatter them elsewhere)
Entity definitions follow Zod Schema First (per docs/web-frontend/typescript.md)
Guide important decisions to also be recorded in docs/domain/decisions.md

Reference Documents

docs/plan/README.md
docs/domain/README.md
docs/backend/server-architecture.md
docs/web-frontend/architecture.md