maiconfz--feature-exploration-planner--feature-intake

Frames feature ideas against repository context and produces intake summaries with blocking questions.

3|1|Updated May 2, 2026
One-click install
npx skills add https://github.com/agents-repo/registry --skill maiconfz-feature-exploration-planner-feature-intake-agents-repo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: maiconfz--feature-exploration-planner--feature-intake
Source: https://github.com/agents-repo/registry/tree/main/.cursor/skills/maiconfz/feature-exploration-planner/maiconfz--feature-exploration-planner--feature-intake
Command: npx skills add https://github.com/agents-repo/registry --skill maiconfz-feature-exploration-planner-feature-intake-agents-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a raw feature idea into a structured, repository-aware intake summary is slow and error-prone, and unclear scope or missing constraints often surface too late. This Skill reads the idea, performs a bounded scan of the host repository, and captures intent plus only the questions that genuinely block progress. ## Core Features & Use Cases - Intent-Preserving Intake Summary: Quotes or faithfully paraphrases the original request and structures problem, users, constraints, and success signals. - Bounded Repository Context: Reads README, specs, rules, and related modules without dumping the whole tree, grounding the summary in real host-repo patterns. - Blocking Questions Only: Separates scope-changing blockers from non-blocking follow-ups and respects prior user clarifications without re-asking. - Use Case: A product manager pastes a rough idea for a new export feature; the Skill reads relevant repo docs and returns an intake-summary plus two blocking questions about target users and data constraints. ## Quick Start Ask the agent to intake this feature idea against the current repository and return an intake summary with any blocking questions.

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

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

FAQPage Schema
How do I turn a rough feature idea into a structured intake summary?▼

Provide the idea as prompt text or a workspace file path. The Skill reads it, scans relevant repository docs and modules, and returns a markdown intake-summary covering problem, users, constraints, and success signals.

What counts as a blocking question in feature intake?▼

A blocking question is one whose answer changes scope, users, constraints, or acceptance criteria. Non-blocking follow-ups are excluded, and the blocking-questions output is empty when no material gaps remain.

Does feature intake modify repository files or write code?▼

No. The Skill only reads repository files such as README, specs, and related modules. It must not implement product code, modify host files, commit, push, or open pull requests.

Can feature intake handle answers from earlier clarification rounds?▼

Yes. It accepts an optional user-clarifications input and applies those answers without re-asking resolved items. When invoked by the planning flow, it returns outputs and stops rather than running its own Q&A loop.

What are the limitations of feature intake compared to full feature research?▼

It deliberately does not produce landscape research or a complete feature brief. Its scope ends at the intake summary and blocking questions; deeper definition belongs to later planning steps.