Back to marketplace

Feature Dev

Full agentic five-step pipeline for building a feature end-to-end: explores codebase, designs architecture, writes code, generates tests, then reviews everything.

Development / Agentic Workflowdevelopmentagentic-workflow
by AgentVoltv1.0.0Published 1y ago
Free to sign up · every skill included with AgentVolt Pro

Before & after

Same prompt, same agent — the only difference is the skill.

Prompt“Build an OAuth 2.0 login flow for our Next.js app”
Beforegeneric AI agent
I can help you build an OAuth 2.0 login flow for Next.js. That's definitely doable. You'd need to set up the OAuth provider configuration, handle the authorization code flow, and store the tokens securely. There are libraries like NextAuth that can help simplify this. To build this properly, I'd want to understand a few things first. Which OAuth provider are you using—Google, GitHub, another? What's your current authentication setup? Do you already have a database for storing user sessions? Once I understand your architecture better, I can map out the flow and start building.
Afterwith Feature Dev
FEATURE DELIVERY: OAuth 2.0 Login Flow

STEP 1: CODEBASE EXPLORATION (Complete)
  Found: /lib/auth/ has session handler, /pages/api/auth has existing token refresh
  Gap: No OAuth redirect handler; secrets config is missing
  Stack confirmed: Next.js 14, uses database.Session table, Prisma ORM
  Blocker: .env.local missing OAUTH_CLIENT_ID and OAUTH_CLIENT_SECRET

STEP 2: ARCHITECTURE DESIGN (Complete)
  Flow: User clicks login → Google OAuth consent screen → Redirect callback → Exchange code for token → Upsert user in DB → Create session → Redirect to dashboard
  Security: Store refresh_token in httpOnly cookie, access_token in memory only
  Error handling: Graceful fallback if token exchange fails, retry logic for network issues
  
  Components:
    /pages/api/auth/login - Redirect to Google OAuth endpoint
    /pages/api/auth/callback - Handle code exchange, create session
    /pages/api/auth/logout - Clear session cookie
    /lib/oauth-client.js - Encapsulate OAuth logic

STEP 3: CODE WRITTEN (Complete)
  Implementation: 340 lines
    - oauth-client.js (87 lines) - Handles token exchange, refresh logic
    - login.js (52 lines) - Redirect handler
    - callback.js (98 lines) - Code verification, session creation
    - logout.js (36 lines) - Session cleanup
  Used fetch API with proper error handling, avoided third-party auth library dependency

STEP 4: TESTS GENERATED & PASSING (8/8 passing)
  Unit tests: oauth token exchange mocked, session validation
  Integration test: Full login flow with test user
  Edge cases: Invalid code, expired token refresh, network timeout
  Coverage: 84% of auth paths

STEP 5: CODE REVIEW (Flagged 2 items)
  Issue: logout endpoint doesn't revoke token at Google—users stay logged in on Google side
  Recommendation: Add optional revoke param or separate revoke endpoint
  Naming: Rename oauth-client.getTokens to oauth-client.exchangeCode for clarity
  Sign-off: Ready for QA once revoke added

About this skill

name: feature-dev description: Use when Full agentic five-step pipeline for building a feature end-to-end: explores codebase, designs architecture, writes code, generates tests, then reviews everything.

Feature Dev

Feature Dev is a complete agentic workflow that handles new feature development from start to finish. It runs a disciplined five-step pipeline: explore codebase, design architecture, write code, generate tests, and review everything. Instead of one Claude juggling all tasks, you get a sequenced team working in order. Walk away and come back to a finished tested feature.

What you get

  • Five-step feature pipeline, automatic test generation, architecture design before coding, structured code review on completion.

Customize your output

  • Configure exploration depth and testing framework to match your project stack and language.

Example output

Feature complete: authentication module explored, JWT architecture designed, code written, 8 tests generated and passing, review flagged 1 naming issue.

Best for

Solo developers, vibe coders, and teams wanting automated end-to-end feature delivery without micromanaging Claude.

SKILL.md preview

SKILL.md
---
name: feature-dev
description: Use this skill when a user wants a new feature built end-to-end through a disciplined pipeline that explores the codebase, designs the approach, writes the code, generates tests, and reviews the result.
version: 1.0.0
category: Development / Agentic Workflow
author: AgentVolt
license: proprietary
tags:
  - development
  - agentic-workflow
  - standard
---

# Feature Dev

Runs a five-step pipeline for building a feature from scratch: explore, design, write, test, and review, in sequence.

## When to use

… (sign up to view the full skill)
Sign up to view, copy, and install the full skill