project-feature

Capture feature requests and write scoped backlog items to TODO.md.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/christophevg/c3 --skill project-feature-christophevg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-feature
Source: https://github.com/christophevg/c3/tree/main/skills/project-feature
Command: npx skills add https://github.com/christophevg/c3 --skill project-feature-christophevg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns vague feature ideas into a structured backlog entry by capturing the request, asking for missing details when needed, and (optionally) producing a fully scoped specification with acceptance criteria.

Core Features & Use Cases

  • Feature intake from minimal prompts: Accepts short requests like “add dark mode” and records them for later scoping.
  • Optional full scoping via interview: Invokes a functional-analyst flow to collect requirements and define acceptance criteria when details are sufficient or the user chooses to proceed.
  • Backlog organization for implementation: Writes results into TODO.md, placing features into unsorted or prioritized sections so /project-manage can implement them later.
  • Use case: When you want to add “user authentication with email/password and OAuth” you can capture it immediately and let the skill drive the scoping conversation and backlog prioritization.

Quick Start

Use the command /project-feature add user authentication with email/password, OAuth (Google, GitHub), and session management.

Frequently Asked Questions about project-feature

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

FAQPage Schema
How do I capture and scope new project feature requests from minimal prompts?

To capture and scope new project feature requests, you can submit a minimal idea like 'add dark mode' and a skill parses its completeness, optionally triggering functional-analyst scoping to define acceptance criteria for the backlog entry.

What is the best way to organize feature intake into a TODO.md backlog?

Organizing feature intake into a TODO.md backlog involves parsing request completeness, optionally interviewing for requirements, and recording the resulting acceptance criteria and dependencies into prioritized or unsorted sections.

Can I record acceptance criteria and dependencies directly from a feature intake interview?

Yes, you can record acceptance criteria and dependencies directly from an interview-driven scoping flow, which collects detailed requirements and writes them into the correct priority section of your TODO.md backlog.

Does project-feature work with YAML-registered skill metadata for requirements scoping?

Yes, project-feature requires YAML-registered skill metadata to execute its intake workflow, parse feature request completeness, and apply functional-analyst scoping for product planning.

When should I not use an interview-driven scoping flow for product planning?

You should not use interview-driven scoping when a feature request lacks sufficient detail or the user chooses not to proceed, allowing the system to simply record the minimal idea as an unsorted TODO.md backlog item instead.