feature-grill

Clarify feature requirements and generate an implementation plan with documented decisions.

Updated Jun 26, 2025

Search Tags:#domain modeling #implementation plan #alignment #feature clarification #contextual documentation

Ready to run

npx skills add https://github.com/flaviogragnolati/coco --skill feature-grill

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a systematic approach to clarify feature requirements and generate an executable implementation plan, bridging the gap between high-level feature requests and actionable development tasks.

Core Features & Use Cases

Feature Clarification: Deep dive into a feature to understand its complexity, interactions, and edge cases.
Implementation Plan Creation: Develop a detailed plan that outlines tasks, dependencies, and validation steps.
Contextual Decision Documentation: Record and maintain terms, assumptions, and architectural decisions in CONTEXT.md.

Quick Start

Activate the feature-grill skill with the command: "Grill the 'user-profile update feature'."

Frequently Asked Questions about feature-grill

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

FAQPage Schema

How do I create an executable implementation plan from a high-level feature request?▼

To create an executable implementation plan, you must clarify feature scope, resolve context, and make domain decisions. This process bridges high-level requests and actionable tasks by generating a detailed plan with validation steps.

What is the best way to document architectural decisions and assumptions during domain modeling?▼

The best way to document architectural decisions during domain modeling is to record terms, assumptions, and context directly in a CONTEXT.md file, ensuring alignment and maintaining contextual documentation alongside the implementation plan.

How does feature clarification work for complex software requirements?▼

Feature clarification works by deep diving into a feature to understand its complexity, interactions, and edge cases. It requires user input on scope and decision-making to ensure the resulting implementation plan is well-defined.

Do I need user input to generate a detailed implementation plan?▼

Yes, user input is required to generate a detailed implementation plan. You must provide information on feature scope, decision-making, and context resolution to ensure the plan is actionable and aligned with project goals.

Can I use this approach to align team understanding before development starts?▼

Yes, you can use this approach to align team understanding before development. It grills features to produce a well-defined, implementation-ready plan and updates contextual documentation to ensure clarity across the team.

What are the limitations of generating implementation plans from feature clarification?▼

A limitation of generating implementation plans is that the Skill requires active user participation for context resolution and decision-making. It cannot autonomously define scope or make architectural decisions without direct user input.