joycraft-new-feature

Guide interview-driven feature discovery into atomic implementation specs.

14|1|Updated Mar 23, 2026

Search Tags:#workflow #specification #decomposition #interview #feature-development #brief #joycraft

Ready to run

npx skills add https://github.com/maksutovic/joycraft --skill joycraft-new-feature

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: joycraft-new-feature
Source: https://github.com/maksutovic/joycraft/tree/main/.agents/skills/joycraft-new-feature
Command: npx skills add https://github.com/maksutovic/joycraft --skill joycraft-new-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams convert vague feature ideas into a structured, interview-driven plan by guiding the user to generate a Feature Brief and decompose work into atomic specs.

Core Features & Use Cases

Interview-centric discovery to elicit goals, constraints, and success criteria.
Feature Brief creation and formalization of scope.
Phase-wise decomposition into atomic specs ready for implementation.

Quick Start

Initiate a new feature workflow with joycraft-new-feature and begin Phase 1: Interview.

Frequently Asked Questions about joycraft-new-feature

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

FAQPage Schema

How do I decompose vague feature ideas into atomic specs for development?▼

Feature decomposition starts with guided interviews to elicit goals and constraints, then formalizes scope into a Feature Brief, and finally breaks work into atomic specs ready for implementation.

What is the best way to structure a feature brief from initial product interviews?▼

A structured feature brief is created through interview-centric discovery to capture success criteria, which then formalizes the project scope before decomposing work into atomic specs.

How does interview-driven feature development improve workflow specification?▼

Interview-driven feature development improves workflow specification by systematically eliciting goals and constraints upfront, ensuring the resulting feature brief and atomic specs align with team expectations.

Can I use guided interviews to define scope for new feature initiatives across product teams?▼

Yes, guided interviews apply directly to new feature initiatives across product teams, helping define scope by capturing goals, constraints, and success criteria before decomposing work.

What are the phases of feature development workflow from interview to tasks?▼

The feature development workflow progresses through three phases: conducting structured interviews, creating a formal feature brief to define scope, and decomposing work into atomic specs.

Do I need prior documentation to start a feature specification workflow?▼

No prior documentation is needed to start a feature specification workflow; you can initiate a new feature workflow and begin directly with Phase 1: Interview to gather requirements.