Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

feature-development-workflow

Sterne23

Forks5

Aktualisiert13. Dezember 2025 um 14:19

Orchestrate end-to-end feature development from requirements through implementation, testing, and review. Use when: (1) planning feature development stages, (2) coordinating multi-agent feature workflows, (3) understanding SDLC phases for new features.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

thapaliyabikendra

thapaliyabikendra/ai-artifacts

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Computersystem- und IT-ManagerFührungsberufe·SOC 11-3021

Datei-Explorer

2 Dateien

SKILL.md

readonly

Mehr aus diesem Repository

gleiches Repository

playwright-integration

thapaliyabikendra/ai-artifacts

Dynamic Playwright E2E testing assistant that adapts to any project type (React, Vue, Angular, Svelte, Next.js, Nuxt, or any web framework). Auto-detects build tools, routing, authentication, and provides tailored setup guidance. **CRITICAL: Never uses hardcoded credentials - always prompts user for valid URLs, environment, and real test credentials before generating login tests.** Use when: (1) setting up Playwright in a new project, (2) configuring Playwright for specific frameworks, (3) debugging framework-specific E2E testing issues, (4) optimizing selectors for React/Vue/Angular components, (5) handling authentication flows in tests (OIDC, JWT, sessions) with proper credential validation.

2026-03-2623

postgresql-query-generation

thapaliyabikendra/ai-artifacts

Generate optimized PostgreSQL queries for Entity Framework Core projects. Automatically discovers domain entities, relationships, and conventions to produce production-ready SQL. Use when: 1. You need complex PostgreSQL queries across multiple related entities 2. Working with ABP Framework and need multi-tenancy/soft delete patterns 3. Querying JSONB fields or need recursive CTEs 4. Building analytics/reporting queries with window functions 5. Optimizing existing queries with proper indexes and joins.

2026-03-2323

user-stories-to-api-spec

thapaliyabikendra/ai-artifacts

Converts requirements written as user stories (.md or .txt) into a structured API Specification document. Defines REST endpoints, request/response shapes, status codes, and permissions for each user story. Output is a .md api-spec file ready to feed into the api-spec-to-technical-plan skill. Use when you have user stories and want a clear API contract before any technical planning or code generation begins.

2026-03-1823

data-seeder-generator

thapaliyabikendra/ai-artifacts

Generate ABP Framework data seeder contributors following project conventions. Auto-detects project structure, existing entities, namespaces, permission constants, and seeder patterns from the codebase — no manual configuration needed. Creates IDataSeedContributor implementations with proper dependency injection, logging, and tenant/feature awareness. Use when: (1) creating new seed data for entities, (2) adding initial/reference data, (3) scaffolding data initialization code, (4) maintaining data consistency across environments.

2026-03-1823

requirements-gap-filler

thapaliyabikendra/ai-artifacts

Checks requirements.md against the actual codebase to find ALL four types of gaps — requirements missing from code, requirements partially implemented, code logic not mentioned in requirements, and business rules in code that were never written into requirements. Automatically updates requirements.md in both directions — flags unimplemented requirements AND adds newly discovered code logic back into requirements. Use after code generation to keep requirements fully in sync with what was actually built.

2026-03-1823

api-spec-to-service

thapaliyabikendra/ai-artifacts

Generate ABP ApplicationService, DTOs, interfaces, and API release documentation from Markdown or OpenAPI/Swagger API specifications. Works with ANY ABP project by auto-detecting existing patterns (response wrappers, error handling, validation, authorization). Use when the user provides an API spec and wants to scaffold services that match their project's conventions and generate release notes.

2026-03-1323

name	feature-development-workflow
description	Orchestrate end-to-end feature development from requirements through implementation, testing, and review. Use when: (1) planning feature development stages, (2) coordinating multi-agent feature workflows, (3) understanding SDLC phases for new features.
layer	4
tech_stack	["agnostic"]
topics	["sdlc","feature-development","orchestration","multi-agent","workflow"]
depends_on	[]
complements	[]
keywords	["Feature","SDLC","Stage","Agent","Workflow","Requirements","Design","Implementation","Test"]

Feature Development Workflow

For complete feature implementation, use the /add-feature command.

Quick Reference

Command	Time	Use Case
`/add-feature <name> "<reqs>" --minimal`	~2 min	Simple CRUD, no docs
`/add-feature <name> "<reqs>" --fast`	~2.5 min	Skip BA, requirements clear
`/add-feature <name> "<reqs>"`	~3 min	Standard (progressive handoff)
`/add-feature <name> "<reqs>" --full-review`	~4.5 min	With code + security review

Dependency Chain (Signal-Based)

BA(entity+perms) ─┬──→ [Architect + QA-Data] ──→ [Developer + QA-Tests]
🟢 ENTITY_READY   │    🟢 CONTRACTS_READY        (parallel implementation)
                  │
BA(reqs+rules) ───┘    (continues in background, non-blocking)

Signal Protocol: Agents emit signals (🟢 ENTITY_READY, 🟢 CONTRACTS_READY) to trigger dependent agents immediately.

Agent Roles

Stage	Agent	Trigger	Output
Analyze	`business-analyst`	Start	Entity definition, permissions, requirements
Design	`backend-architect`	🟢 ENTITY_READY	Technical design, interface contracts
Test Data	`qa-engineer`	🟢 ENTITY_READY	TestData.cs, Seeder.cs (parallel with Architect)
Implement	`abp-developer`	🟢 CONTRACTS_READY	Domain, Application, EF Core layers
Tests	`qa-engineer`	🟢 CONTRACTS_READY	Unit tests (parallel with Developer)
Review	`abp-code-reviewer`	Phase 2 complete	Review report (optional)
Security	`security-engineer`	Phase 2 complete	Security audit (optional)

Parallelism Optimizations

Phase 1b: Architect + QA-Data run in parallel (on ENTITY_READY)
Phase 2: Developer + QA-Tests run in parallel (on CONTRACTS_READY)
BA secondary outputs: Non-blocking (requirements.md, business-rules.md)
Skipped by default: ANALYSIS.md, impact-analysis.md (use --impact flag)

Full Documentation

See .claude/commands/feature/add-feature.md for complete workflow documentation.