Full-Stack Feature Development Skill

yes

Updated Jan 14, 2026
One-click install
npx skills add https://github.com/byteAgenten/byteagenten-marketplace --skill full-stack-feature-development-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Full-Stack Feature Development Skill
Source: https://github.com/byteAgenten/byteagenten-marketplace/tree/main/plugins/byt8/skills/full-stack-feature
Command: npx skills add https://github.com/byteAgenten/byteagenten-marketplace --skill full-stack-feature-development-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill orchestrates and automates the end-to-end workflow for developing a new full-stack feature, coordinating role-based agents and enforcing governance through hooks and state management.

Core Features & Use Cases

  • Deterministic phase flow: controls phases 0–9 with auto-advance and mandatory approvals.
  • Hook-driven governance: pre-tool-use blockers and stop/hooks enforce safe edits and scoped exploration.
  • State-aware collaboration: uses a structured workflow-state.json to track progress, approvals, and rollbacks.
  • Use Case: When starting a new feature, the Skill guides architect-planner, UI designer, API architect, and other roles through design, implementation, and review with minimal manual intervention.

Quick Start

Start the workflow by cleaning up any previous run, initialize state, and launch Phase 0 with the architect-planner task.

Frequently Asked Questions about Full-Stack Feature Development Skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate a full-stack feature development workflow with multiple phases?

Automate full-stack feature development by configuring a hook-driven workflow that orchestrates phases 0–9 with auto-advance and mandatory approval gates. Specialized agents handle design, API, UI, and QA tasks sequentially.

How do approval gates work in automated full-stack development workflows?

Approval gates in automated full-stack workflows function as deterministic phase controls using pre-tool-use hooks. These hooks block unsafe edits and require explicit approval before the workflow advances to the next development stage.

What is hook-driven governance for software engineering workflows?

Hook-driven governance for software engineering workflows is a mechanism using pre-tool-use blockers and stop hooks to enforce safe edits and scoped exploration, ensuring deterministic phase control and structured progression across multi-agent tasks.

Can I use a structured state file to track progress and rollbacks in full-stack development?

You can track progress and manage rollbacks in full-stack development using a structured workflow-state.json file. This state-aware collaboration mechanism records approvals and maintains deterministic phase flow throughout the feature lifecycle.

Does full-stack feature development automation support multi-agent collaboration?

Full-stack feature development automation supports multi-agent collaboration by coordinating role-based agents like architect-planner, UI designer, and API architect through a deterministic, state-managed workflow with minimal manual intervention.

What are the limitations of using deterministic hooks for full-stack workflow automation?

Deterministic hooks for full-stack workflow automation require strict phase adherence, meaning any step outside the configured 0–9 phase flow or unscoped exploration will be blocked by pre-tool-use governance, limiting ad-hoc modifications.