How do I install the Workflow Feature Development skill?

Run npx skillmds@latest add tomevault-io/workflow-feature-development in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Workflow Feature Development safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Workflow Feature Development?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Workflow Feature Development free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Workflow Feature Development?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Workflow Feature Development by tomevault-io

Name: Workflow Feature Development
Author: tomevault-io

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. Use when this capability is needed.

tomevault-io c7005e0 2 files · 2.8 KB Updated Sep 17, 2026

File contents

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

Revert database migrations
Restore previous version
Notify stakeholders

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: workflow-feature-developmentdescription: Complete workflow for developing new features from design to deployment. Use when starting a new feature, adding functionality, or building something new. Use when this capability is needed.---# Feature Development WorkflowStep-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 Plan1. Revert database migrations2. Restore previous version3. Notify stakeholders---> Converted and distributed by [TomeVault](https://tomevault.io/claim/nickcrew) — claim your Tome and manage your conversions.

Frequently asked questions