AI Agent Skill HUB

workflow-feature

Complete feature development workflow from design to deployment. Use when implementing new features or functionality.

13 stars
byNickCrew
View on GitHubInstallation ↓

Best use case

workflow-feature is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Complete feature development workflow from design to deployment. Use when implementing new features or functionality.

Teams using workflow-feature 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

$curl -o ~/.claude/skills/workflow-feature/SKILL.md --create-dirs "https://raw.githubusercontent.com/NickCrew/Claude-Cortex/main/skills/workflow-feature/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/workflow-feature/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How workflow-feature Compares

Feature / Agentworkflow-featureStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Complete feature development workflow from design to deployment. Use when implementing new features or functionality.

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 Development Workflow

Complete workflow for developing new features from design to deployment.

## Phases

### 1. Architecture Design
**Define:**
- Component structure
- Data models
- API contracts
- Integration points
- Dependencies

**Output:** Architecture diagram, component list, API specs

**Agent:** `architect-review` for complex features

### 2. Implementation Planning
**Break down into:**
- Discrete tasks (< 2 hours each)
- Dependencies between tasks
- Parallel workstreams

**Output:** Task list with estimates

### 3. Implementation
**Guidelines:**
- Write tests alongside code (TDD optional but helpful)
- Commit frequently (atomic commits)
- Follow existing patterns in codebase
- Document as you go

**Run parallel workstreams:**
- Core implementation
- Tests
- Documentation

### 4. Code Review
**Checklist:**
- [ ] Code follows project conventions
- [ ] No obvious bugs or edge cases missed
- [ ] Performance acceptable
- [ ] Error handling complete
- [ ] Tests meaningful (not just coverage)

**Agent:** `code-reviewer`

### 5. Security Review
**Check:**
- Input validation
- Auth/authz on new endpoints
- Sensitive data handling
- No secrets in code

**Agent:** `security-auditor` (if auth-related)

### 6. Testing
**Required:**
- Unit tests (80%+ coverage on new code)
- Integration tests for API endpoints
- E2E tests for critical paths

**Agent:** `test-automator` or `debugger`

### 7. Performance Check
**Verify:**
- Response times acceptable
- No memory leaks
- Bundle size impact (frontend)

**Agent:** `performance-engineer` (if perf-sensitive)

### 8. Documentation
**Update:**
- API docs (OpenAPI/Swagger)
- User guide (if user-facing)
- Changelog entry
- README if needed

### 9. Deployment Prep
**Checklist:**
- [ ] Version bumped
- [ ] Changelog updated
- [ ] Migration scripts (if DB changes)
- [ ] Rollback plan documented
- [ ] Feature flags (if gradual rollout)

## Success Criteria
- [ ] All tests pass
- [ ] Security review clean
- [ ] Performance within limits
- [ ] Documentation complete
- [ ] Code reviewed and approved

## Review Gate
```bash
# Run before marking complete
cortex review -c feature
```

## Quick Start Template

```markdown
## Feature: [Name]

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

### Tasks
- [ ] Task 1
- [ ] Task 2
- [ ] Tests
- [ ] Docs

### API Changes
- `POST /api/v1/resource` - Create resource
- `GET /api/v1/resource/:id` - Get resource

### Rollback Plan
1. Revert commit
2. Run down migration
3. Clear cache
```

Related Skills

We are still matching the closest adjacent skills for this page. In the meantime, continue through the full directory.