feature

Implement production-ready features across database, backend, and frontend layers with incremental phased approach

8 stars

Best use case

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

Implement production-ready features across database, backend, and frontend layers with incremental phased approach

Teams using 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/feature/SKILL.md --create-dirs "https://raw.githubusercontent.com/dhofheinz/open-plugins/main/plugins/10x-fullstack-engineer/commands/feature/skill.md"

Manual Installation

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

How feature Compares

Feature / AgentfeatureStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Implement production-ready features across database, backend, and frontend layers with incremental phased approach

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 Implementation Router

Comprehensive feature implementation across the full stack with phased, incremental development approach. Routes feature implementation requests to specialized operations for different layers or full-stack implementation.

## Operations

- **implement** - Complete full-stack feature implementation across all layers (database, backend, frontend, integration)
- **database** - Database layer only (migrations, models, schemas, indexes)
- **backend** - Backend layer only (services, API endpoints, validation, tests)
- **frontend** - Frontend layer only (components, state, API integration, tests)
- **integrate** - Integration and polish phase (E2E tests, performance, security, documentation)
- **scaffold** - Scaffold feature structure and boilerplate across all layers

## Usage Examples

```bash
# Complete full-stack feature
/feature implement description:"user authentication with OAuth and 2FA" tests:"comprehensive"

# Database layer only
/feature database description:"user profiles table with indexes" migration:"add_user_profiles"

# Backend API only
/feature backend description:"REST API for product search with filters" validation:"strict"

# Frontend components only
/feature frontend description:"product catalog with infinite scroll and filters" framework:"react"

# Integration and polish
/feature integrate feature:"authentication flow" scope:"E2E tests and performance"

# Scaffold feature structure
/feature scaffold name:"notification-system" layers:"database,backend,frontend"
```

## Router Logic

Parse the first word of $ARGUMENTS to determine operation:

1. Extract operation from first word of $ARGUMENTS
2. Extract remaining arguments as operation parameters
3. Route to instruction file:
   - "implement" → Read `.claude/commands/fullstack/feature/implement.md` and execute
   - "database" → Read `.claude/commands/fullstack/feature/database.md` and execute
   - "backend" → Read `.claude/commands/fullstack/feature/backend.md` and execute
   - "frontend" → Read `.claude/commands/fullstack/feature/frontend.md` and execute
   - "integrate" → Read `.claude/commands/fullstack/feature/integrate.md` and execute
   - "scaffold" → Read `.claude/commands/fullstack/feature/scaffold.md` and execute

4. Pass extracted parameters to the instruction file
5. Return structured implementation

**Error Handling:**
- If operation is unrecognized, list available operations with examples
- If parameters are missing, request clarification with expected format
- If requirements are unclear, ask specific questions about scope and acceptance criteria
- Provide clear error messages with usage examples

**Security:**
- Validate all input parameters
- Ensure no hardcoded secrets in generated code
- Follow security best practices for each layer
- Include validation and sanitization in generated code

---

**Base directory:** `.claude/commands/fullstack/feature`
**Current Request:** $ARGUMENTS

Parse operation and route to appropriate instruction file now.

Related Skills

specification-writing

8
from dhofheinz/open-plugins

Core reference for EARS requirement patterns, Given/When/Then acceptance criteria, RFC 2119 language, requirement ID conventions, and specification quality checklists. Background knowledge for the spec-writer agent. Preloaded by spec-writer via the skills frontmatter field; not user-invocable.

refine

8
from dhofheinz/open-plugins

Unified specification refinement plugin. Single entry point for all spec operations: greenfield architecture pipelines (principles → design → stack → spec → plan), feature spec creation in existing systems, iterative convergence loops, quality reviews, drift detection, finalization, ticket decomposition, traceable updates, and lifecycle archival. Detects pipeline state from existing artifact frontmatter and routes intelligently. Use whenever you need to create, refine, validate, or evolve a technical specification.

validation-orchestrator

8
from dhofheinz/open-plugins

Intelligent validation orchestrator with auto-detection and progressive validation workflows

security-scan

8
from dhofheinz/open-plugins

Comprehensive security scanning for secrets, vulnerabilities, and unsafe practices

schema-validation

8
from dhofheinz/open-plugins

Validate JSON schemas, required fields, and format compliance for marketplaces and plugins

quality-analysis

8
from dhofheinz/open-plugins

Deep quality analysis with scoring, recommendations, and actionable reports

documentation-validation

8
from dhofheinz/open-plugins

Validate documentation completeness, format, and quality for plugins and marketplaces

best-practices

8
from dhofheinz/open-plugins

Enforce OpenPlugins and Claude Code best practices for naming, versioning, and standards compliance

message-generation

8
from dhofheinz/open-plugins

Generate conventional commit messages following best practices

history-analysis

8
from dhofheinz/open-plugins

Analyze git history to learn project's commit style and conventions

commit-error-handling

8
from dhofheinz/open-plugins

Handle git errors and edge cases gracefully

commit-best-practices

8
from dhofheinz/open-plugins

Enforce git commit best practices and workflow guidance