fullstack feature

Engineering Community

Skill notes

Resources

Fullstack Feature Orchestration This skill defines the end-to-end workflow for implementing complete features that span multiple layers of the stack. It orchestrates specialized agents through 7 distinct phases, from requirements clarification through delivery.

When to Use This Skill

Use fullstack-feature when the user requests: A complete feature that requires database, API, and UI changes End-to-end implementation with testing and review A new user-facing capability that touches multiple components Anything described as: "build X", "add X feature", "implement X capability"

Overview

The fullstack feature workflow consists of 7 phases: Understand - Clarify requirements, load skills, identify affected layers Foundation (sequential) - Database schema/migrations, type generation Core Implementation (parallel) - API endpoints, UI components, state management Integration (sequential) - Wire UI to API, state to UI, verify data flow

Runtime Engine and WRFC Chains

The runtime engine automatically creates a WRFC (Work-Review-Fix-Complete) chain for each work agent. When an agent completes its work and emits a <gv> tag, the runtime: Evaluates the output against the configured min_review_score (default: 9.5 from goodvibes.json) Issues directives to the orchestrator via system messages Orchestrator executes those directives mechanically Directive types:

Purpose

Ensure you have complete clarity on what to build before spawning work agents. This phase prevents wasted effort from misunderstandings.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@diegosouzapw · no license declared
Token usage
Heavy
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1: Understand

Phase 1: Understand

02
Phase 2: Foundation (Sequential)

Phase 2: Foundation (Sequential)

03
Phase 3: Core Implementation (Parallel)

Phase 3: Core Implementation (Parallel)

04
Phase 4: Integration (Sequential)

Phase 4: Integration (Sequential)

05
Phase 5: Quality (Parallel)

Phase 5: Quality (Parallel)

06
Phase 6: Review (Runtime-Driven)

Phase 6: Review (Runtime-Driven)

07
Phase 7: Commit + Log

Phase 7: Commit + Log

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.