feature

Coordinate feature development through a structured seven-phase workflow.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/jamiegrand/cleo-web --skill feature-jamiegrand
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature
Source: https://github.com/jamiegrand/cleo-web/tree/main/.claude/skills/feature
Command: npx skills add https://github.com/jamiegrand/cleo-web --skill feature-jamiegrand

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Feature development often lacks a repeatable structure, leading to miscommunication, scope drift, and missed documentation. This skill provides a rigorous, seven-phase workflow to plan, validate, and ship features with built-in governance and documentation lookups.

Core Features & Use Cases

  • Structured seven-phase workflow guiding feature delivery from CLARIFY to SHIP for consistent outcomes
  • Documentation consultation via astro docs MCP to inform decisions and reduce ambiguity
  • State persistence across sessions to pause and resume work without loss
  • Plan-driven execution with explicit outputs, milestones, and commit-ready artifacts
  • Integration-ready prompts and guardrails (disable-model-invocation available) for safe AI interaction

Quick Start

Run /feature to start a new feature and guide it through the seven-phase workflow.

Frequently Asked Questions about feature

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

FAQPage Schema
What is a structured workflow for feature development and when do I need it?

A structured feature development workflow prevents scope drift and miscommunication by guiding delivery through sequential phases. You need this process when your software projects require rigorous planning, documentation lookups, and progress tracking across multiple sessions or teams.

How do I manage feature development across multiple sessions without losing progress?

Feature development across sessions uses state persistence to pause and resume work without loss. The workflow maintains progress tracking and plan-driven milestones, ensuring you can stop and restart the end-to-end delivery process seamlessly.

How do I plan and execute software features with built-in documentation lookups?

You plan and execute features using a seven-phase workflow from clarify to ship. It consults astro docs MCP during the process to inform decisions, reducing ambiguity and generating commit-ready artifacts with explicit outputs.

Does this feature workflow support astro docs MCP for reducing ambiguity?

Yes, the feature workflow integrates astro docs MCP for documentation consultation. This mechanism informs technical decisions during the analyze and plan phases, reducing ambiguity and ensuring validated feature delivery.

What are the limitations of using a plan-driven workflow for software feature delivery?

A plan-driven workflow requires strict adherence to its seven phases, which may feel rigid for rapid prototyping. However, it provides guardrails and integration-ready prompts to ensure safe AI interaction and consistent feature outcomes.