skills.rest
agents-repo
agents-repoOFFICIAL
Explore all skills by this author →
WebsiteGitHub

maiconfz--feature-exploration-planner--feature-definition-planner

Synthesizes feature-brief markdown from intake, landscape, and options artifacts.

3|1|Updated May 2, 2026
Search Tags:#markdown#acceptance criteria#product planning#feature brief#issue planning#requirements synthesis
One-click install
npx skills add https://github.com/agents-repo/registry --skill maiconfz-feature-exploration-planner-feature-definition-planner-agents-repo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: maiconfz--feature-exploration-planner--feature-definition-planner
Source: https://github.com/agents-repo/registry/tree/main/.cursor/skills/maiconfz/feature-exploration-planner/maiconfz--feature-exploration-planner--feature-definition-planner
Command: npx skills add https://github.com/agents-repo/registry --skill maiconfz-feature-exploration-planner-feature-definition-planner-agents-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning scattered exploration notes—intake summaries, landscape research, and options comparisons—into a single coherent feature brief is tedious and error-prone. This Skill consolidates all prior planning artifacts into one structured markdown brief while preserving the user's original intent. ## Core Features & Use Cases - Brief Synthesis: Combines feature-idea, intake-summary, landscape-report, options-summary, and user-clarifications into a single feature-brief markdown document. - Structured Output: Produces problem statement, success criteria, recommended approach, scope boundaries, open questions, and a copy-paste-ready GitHub issue title with acceptance criteria. - Intent Preservation: Distinguishes what the user asked for from what is recommended, and never silently changes stated scope or constraints. - Use Case: After running intake, landscape research, and options analysis for a new product feature, invoke this Skill to produce the final planning brief ready for issue creation or implementation planning. ## Quick Start Ask the agent to synthesize a feature brief from your feature idea, intake summary, landscape report, and options summary artifacts.

Frequently Asked Questions about maiconfz--feature-exploration-planner--feature-definition-planner

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

FAQPage Schema
How do I generate a feature brief from exploration artifacts?▼

Provide the feature-idea, intake-summary, landscape-report, and options-summary as inputs. The Skill synthesizes them into a markdown feature-brief covering problem statement, recommended approach, scope boundaries, and acceptance criteria in one shot.

What inputs are required to create a feature brief?▼

A non-empty feature-idea is mandatory, along with intake-summary, landscape-report, and options-summary. User-clarifications are optional. The Skill refuses to produce a brief without a non-empty feature-idea.

Can the feature brief be used to create GitHub issues?▼

Yes, the brief includes a suggested issue title and a copy-paste-ready acceptance criteria block formatted for GitHub. However, the Skill itself never calls gh or creates issues; that handoff is manual or done by the invoking flow.

Does the feature definition planner modify files or code?▼

No, it is planning-only. It must not implement product code, modify host files, commit, push, or open pull requests. Write-back to an output path is handled by the parent flow, not this Skill.

What happens when inputs are incomplete or unclear?▼

The Skill does not enter a Q&A loop. It labels assumptions, places non-blocking follow-ups in the open-questions output, and stops. Blocking issues mean the brief is not produced without a valid feature-idea.

Related Skills

Explore More Product & Management Skills→
four43four43
4

business-analysis

Conduct web-based business analyses with strategic frameworks and cited reports.

Community
Advanced
4asaanAI4asaanAI

user-story

Convert feature descriptions into user stories with acceptance criteria and effort estimates.

Community
Intermediate
coolbeevipcoolbeevip
8

team-tech-debt-review

Review technical debt risk, priority, and readiness for issue breakdown.

Community
Intermediate
chiruu12chiruu12
1

spec-driven-development

Create and review software specifications before implementation begins.

Community
Intermediate