build-feature

Collect intake questionnaires and produce decision-ready feature plans.

Updated Aug 23, 2026

Search Tags:#decisions #roadmap #spec #plan #feature #intake

Ready to run

npx skills add https://github.com/narduk-enterprises/myboat --skill build-feature-narduk-enterprises

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: build-feature
Source: https://github.com/narduk-enterprises/myboat/tree/main/.github/skills/build-feature
Command: npx skills add https://github.com/narduk-enterprises/myboat --skill build-feature-narduk-enterprises

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps teams convert vague feature requests into an implementation-ready plan with clearly defined scope, decisions, and criteria so engineers can implement without guessing.

Core Features & Use Cases

Consolidated intake: one structured questionnaire surfaces decisions, assumptions, blockers, and scope boundaries.
Decision-complete plan: outputs a concrete plan ready for execution, including affected routes, data changes, and rollout considerations.
Guardrails and alignment: ensures compatibility with existing systems and clarifies what is in and out of scope.

Quick Start

Provide a feature brief and let the system generate a decision-ready feature plan.

Frequently Asked Questions about build-feature

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

FAQPage Schema

How do I turn a vague feature request into a ready feature plan?▼

To turn a vague feature request into a ready feature plan, provide an initial brief. The system applies an intake questionnaire to surface decisions, assumptions, and blockers, producing a decision-complete plan ready for handoff.

What is a decision-complete feature plan?▼

A decision-complete feature plan is a concrete output detailing scope boundaries, affected routes, data changes, and rollout considerations. It ensures engineers can implement without guessing or needing further alignment.

How do I scope a feature spanning UI, backend, and data integrations?▼

Scoping a feature spanning UI, backend, data, or integrations requires clarifying boundaries. A structured intake process consolidates system compatibility guardrails and rollout criteria into a decision-ready plan.

Does this feature planning process capture assumptions and blockers?▼

Yes, the feature planning process captures assumptions and blockers. The consolidated intake questionnaire specifically surfaces these elements alongside decisions and scope boundaries to ensure alignment before implementation begins.

Can I use this for product roadmap planning and feature intake?▼

Yes, you can use this for product roadmap planning and feature intake. It translates vague requests into structured plans by defining scope boundaries, affected data changes, and rollout considerations to align with roadmap decisions.