skills.rest
jammindev
jammindevOFFICIAL
Explore all skills by this author →
GitHub

prepare-feature

Scope features into product documentation, technical backlog, and GitHub-ready issues.

Updated Sep 21, 2025
Search Tags:#documentation#feature planning#github issues#scope definition#product spec#technical backlog
One-click install
npx skills add https://github.com/jammindev/house --skill prepare-feature
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prepare-feature
Source: https://github.com/jammindev/house/tree/main/.claude/skills/prepare-feature
Command: npx skills add https://github.com/jammindev/house --skill prepare-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn an idea into a clear implementation plan before any code is written, so teams can align on scope, product intent, technical breakdown, and GitHub tracking without churn later.

Core Features & Use Cases

  • Product framing: Define the user problem, V1 scope, and what is deliberately deferred.
  • Concept documentation: Create a concept lesson when the feature introduces non-trivial ideas that need onboarding or architectural explanation.
  • Technical backlog design: Break the work into actionable lots with file-level targets, acceptance criteria, and issue-ready structure.
  • GitHub issue planning: Prepare parent and child issues with the right labels and cross-links for execution.

Quick Start

Ask the skill to prepare the feature documentation, concept note, technical backlog, and GitHub issues for the chantier you want to scope.

Frequently Asked Questions about prepare-feature

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

FAQPage Schema
How do I scope a feature into product documentation and GitHub issues?▼

Feature scoping translates a feature idea into product documentation, concept notes, technical backlog, and GitHub-ready issues with explicit scope, file targets, and acceptance criteria before implementation begins.

What is the best way to define V1 boundaries for new modules before coding?▼

Defining V1 boundaries involves creating a technical backlog that breaks work into actionable lots with file-level targets and issue-ready structure, deliberately deferring out-of-scope items to prevent churn later.

How do I break down a product spec into a technical backlog for cross-cutting platform work?▼

Breaking down a product spec involves generating a technical backlog with explicit file targets, acceptance criteria, and structured issue breakdowns to align teams on technical execution without writing application code.

Does feature planning require structured deliverables for user-facing changes?▼

Feature planning requires structured deliverables including product documentation, concept notes for non-trivial ideas, and cross-linked GitHub issues to ensure clear V1 boundaries for user-facing changes.

Can I prepare parent and child GitHub issues with cross-links during pre-implementation planning?▼

Pre-implementation planning includes preparing parent and child GitHub issues with appropriate labels and cross-links, ensuring execution teams have actionable, properly tracked tasks for the defined scope.

When should I not use automated feature scoping for my project?▼

Automated feature scoping should not be used when application code generation is required immediately, as it focuses exclusively on pre-implementation planning, documentation, and issue breakdown rather than writing code.

Related Skills

Explore More Product & Management Skills→
cpfcoachingcpfcoaching

idea-refine

Guide users through divergent and convergent thinking to refine ideas into actionable concepts.

Community
Advanced
TasupTasup
2

update-parent-issue-status

Update parent GitHub Issues based on child issue status changes.

Official
Advanced
JoeyJoziahJoeyJoziah

github-project-management

Organize GitHub issues, project boards, and sprint workflows.

Community
Advanced
posit-devposit-dev
4.2k

positron-issue-creator

Drafts complete GitHub issue drafts for the Positron repository with duplicate checking.

Official
Basic