Feature Intake
Parse and normalize features from text descriptions, images, and screenshots into structured requirements.
Best use case
Feature Intake is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Parse and normalize features from text descriptions, images, and screenshots into structured requirements.
Teams using Feature Intake should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/feature-intake/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How Feature Intake Compares
| Feature / Agent | Feature Intake | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Parse and normalize features from text descriptions, images, and screenshots into structured requirements.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Feature Intake Parse and normalize features from text descriptions, images, and screenshots into structured requirements. ## Agent Feature Planner - `automaker-feature-planner` ## Workflow 1. Parse feature title and description text 2. Analyze attached images and screenshots for UI requirements 3. Extract explicit and implicit requirements 4. Categorize feature type (UI, API, infrastructure, refactor, bugfix) 5. Estimate initial complexity 6. Extract acceptance criteria ## Inputs - `projectName` - Project name - `feature` - Feature object with id, title, description, attachments ## Outputs - Parsed feature with extracted requirements, type, complexity, and acceptance criteria ## Process Files - `automaker-feature-pipeline.js` - Stage 1 - `automaker-orchestrator.js` - Phase 1
Related Skills
Feature Flagging
Feature flag configuration and rollout planning for controlled releases
feast-feature-store
Feature store management skill for online/offline feature serving, feature registration, and training-serving consistency.
Feature Engineering Optimizer
Optimizes feature engineering pipelines and feature store configurations
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
yolo
Run Babysitter autonomously with minimal manual interruption.
user-install
Install the user-level Babysitter Codex setup.
team-install
Install the team-pinned Babysitter Codex workspace setup.
retrospect
Summarize or retrospect on a completed Babysitter run.
resume
Resume an existing Babysitter run from Codex.
project-install
Install the Babysitter Codex workspace integration into the current project.
plan
Plan a Babysitter workflow without executing the run.