# Create Feature Task

> Use when creating a new feature development task — scaffolds a structured task file at .claude/tasks/{feature-name}.md with phased breakdown (Design, Implementation, Testing, Documentation), acceptance criteria, context preservation, and TaskCreate tracking. Activates on "create a feature task", "set up development tracking", "plan a feature implementation", or when preparing work for python-cli-architect or python-pytest-architect agents.

- Skill: `jamie-bitflight/create-feature-task` (Agent Skill)
- Install (CLI): `npx skillmds@latest add jamie-bitflight/create-feature-task`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jamie-bitflight/create-feature-task/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: Jamie-BitFlight (https://skillmd.com/u/jamie-bitflight)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/jamie-bitflight/create-feature-task

---


# Create Feature Development Task

Set up a comprehensive feature development task with proper tracking, phases, and documentation.

## Execution Steps

Load and follow the standards in `/python-engineering:standards-for-python-development` when applying shared architecture, typing, testing, or CLI rules.

### 1. Parse Feature Requirements

- Extract feature name and description from arguments
- Identify key requirements and constraints
- Determine complexity and scope

### 2. Generate Task Structure

- Customize phases based on feature type
- Add specific acceptance criteria
- Include relevant technical considerations

### 3. Create Task Documentation

Create task file at `.claude/tasks/{feature-name}.md` with:

```markdown
# Feature: {Feature Name}

## Overview
{Brief description}

## Requirements
- [ ] Requirement 1
- [ ] Requirement 2

## Technical Approach
{High-level design}

## Phases

### Phase 1: Design
- [ ] Review existing patterns
- [ ] Create interface definitions
- [ ] Document edge cases

### Phase 2: Implementation
- [ ] Core functionality
- [ ] Error handling
- [ ] Integration points

### Phase 3: Testing
- [ ] Unit tests (80% minimum coverage)
- [ ] Integration tests
- [ ] Edge case coverage

### Phase 4: Documentation
- [ ] Code documentation
- [ ] Usage examples
- [ ] API documentation (if applicable)

## Acceptance Criteria
- [ ] All tests pass
- [ ] Coverage meets minimum
- [ ] Documentation complete
- [ ] Code review approved

## Context Preservation
- Initial requirements: {captured}
- Key decisions: {recorded}
- Dependencies: {identified}
- Risks: {noted}
```

### 4. Set Up Tracking

- Add task to TODO list using TaskCreate tool
- Create initial checkpoints
- Set up progress markers

## Context Preservation

When creating tasks, preserve:

- Initial requirements from user
- Key technical decisions made
- File locations involved
- Dependencies identified
- Risk factors noted

## Integration

| Step          | Command/Action                                         |
| ------------- | ------------------------------------------------------ |
| Prerequisites | Clear feature requirements                             |
| Follow-up     | Use `python-engineering:python-cli-architect` agent for implementation    |
| Related       | `python-engineering:comprehensive-test-review`, `python-engineering:python-pytest-architect` |

## Example Usage

```text
/python-engineering:create-feature-task Add user authentication with OAuth2 support
/python-engineering:create-feature-task Implement rate limiting for API endpoints
/python-engineering:create-feature-task Create CLI command for database migrations
```