Agent skill

workflow-feature-development

Complete workflow for developing new features from design to deployment. Use when starting a new feature, adding functionality, or building something new.

Stars 13
Forks 6

Install this agent skill to your Project

npx add-skill https://github.com/NickCrew/Claude-Cortex/tree/main/skills/workflow-feature-development

SKILL.md

Feature Development Workflow

Step-by-step process for developing features properly.

Phase 1: Design

Agents: system-architect

  • Design feature architecture
  • Identify components and boundaries
  • Define API contracts
  • Document data flow

Output: Architecture diagram, component list, API contracts

Phase 2: Planning

Agents: requirements-analyst

  • Break down into implementable tasks
  • Identify dependencies
  • Estimate timeline
  • Define acceptance criteria

Output: Task breakdown, dependency graph, timeline

Phase 3: Implementation

  • Implement feature following architecture
  • Work in small, testable increments
  • Commit frequently with clear messages

Phase 4: Review

Agents: code-reviewer, security-auditor

  • Code review for quality and standards
  • Security review for vulnerabilities
  • Focus: auth, input validation, data access

Blocking: Must pass before proceeding

Phase 5: Testing

Agents: test-automator

  • Unit tests (80% coverage target)
  • Integration tests
  • E2E tests for critical paths

Phase 6: Performance

Agents: performance-engineer

Validate against thresholds:

  • Response time: <200ms
  • Memory usage: <100MB
  • Bundle size: <500KB

Phase 7: Documentation

Agents: technical-writer

  • API documentation
  • User guide updates
  • Changelog entry

Phase 8: Deployment Prep

Agents: deployment-engineer

Checklist:

  • Version bump
  • Changelog updated
  • Migration scripts ready
  • Rollback plan documented

Success Criteria

  • All tests pass
  • Security scan clean
  • Performance within limits
  • Documentation complete

Rollback Plan

  1. Revert database migrations
  2. Restore previous version
  3. Notify stakeholders

Expand your agent's capabilities with these related and highly-rated skills.

NickCrew/Claude-Cortex

claude-consult

Consult Claude specialist agents during implementation for codebase understanding, pattern checking, security review, debugging help, and more. Use this skill whenever you're unsure about conventions, stuck on a failure, or need expert input before writing code. Does not replace the formal review gates in agent-loops — this is for mid-implementation consultation.

13 6
Explore
NickCrew/Claude-Cortex

doc-quality-review

Assess documentation quality across readability, consistency, audience fit, and prose clarity. Produces a scored review with actionable findings. This skill should be used before releases, during doc reviews, or when documentation feels unclear or inconsistent.

13 6
Explore
NickCrew/Claude-Cortex

event-driven-architecture

Event-driven architecture patterns with event sourcing, CQRS, and message-driven communication. Use when designing distributed systems, microservices communication, or systems requiring eventual consistency and scalability.

13 6
Explore
NickCrew/Claude-Cortex

prompt-engineering

Optimize prompts for LLMs and AI systems with structured techniques, evaluation patterns, and synthetic test data generation. Use when building AI features, improving agent performance, or crafting system prompts.

13 6
Explore
NickCrew/Claude-Cortex

compliance-audit

Regulatory compliance auditing across GDPR, HIPAA, PCI DSS, SOC 2, and ISO frameworks with automated evidence collection and gap analysis. Use when conducting compliance assessments, preparing for certifications, or implementing regulatory controls.

13 6
Explore
NickCrew/Claude-Cortex

react-performance-optimization

React performance optimization patterns using memoization, code splitting, and efficient rendering strategies. Use when optimizing slow React applications, reducing bundle size, or improving user experience with large datasets.

13 6
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results