start-workflow-fs

Orchestrate parallel frontend and backend workflows with fixed contracts and integrated validation.

1|1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/kangmomin/harness-plugins --skill start-workflow-fs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start-workflow-fs
Source: https://github.com/kangmomin/harness-plugins/tree/main/plugins/hyeondongs-harness/skills/start-workflow-fs
Command: npx skills add https://github.com/kangmomin/harness-plugins --skill start-workflow-fs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Start Workflow Full Stack — Agile Orchestrator helps teams avoid monolithic implementations by decoupling frontend and backend work, fixing functionality and communication contracts upfront, and coordinating independent components through iterative reviews and integrated validation.

Core Features & Use Cases

  • Feature-first planning: define user-facing functionality and success criteria before coding.
  • Contract-first integration: lock frontend-backend interfaces, data models, and communication protocols early.
  • Parallel implementation and integration: run frontend and backend work concurrently, then verify end-to-end behavior.
  • Real-world Use Case: when a UI changes alongside an API, this skill aligns contracts and enables parallel delivery with rapid validation.

Quick Start

Describe a feature to implement, fix its functionality and communication contracts, then start parallel frontend and backend work followed by integrated validation.

Frequently Asked Questions about start-workflow-fs

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

FAQPage Schema
How do I coordinate parallel frontend and backend development without contract drift?

Parallel frontend and backend development requires fixing communication contracts and data models upfront before implementation. This orchestrator enforces phase-based collaboration and ownership separation to prevent contract drift, ensuring both sides align interfaces early.

What is contract-first full-stack workflow orchestration?

Contract-first full-stack workflow orchestration is a phase-driven process that locks frontend-backend interfaces and communication protocols before coding begins. It automates parallel implementation followed by integrated validation to verify end-to-end behavior across independent components.

How do I start a cross-cutting feature workflow where UI and API evolve together?

Describe the user-facing feature, fix its functionality and communication contracts, then start parallel frontend and backend work followed by integrated validation. This decouples workstreams while coordinating independent components through iterative reviews.

Can I use this agile orchestrator for monolithic implementations?

This agile orchestrator is designed for decoupled full-stack delivery, not monolithic implementations. It enforces ownership separation and phase-based collaboration to prevent contract drift, making it suited for cross-cutting features requiring parallel development.

Does full-stack parallel development work without upfront contract reviews?

Full-stack parallel development requires upfront contract reviews to prevent integration failures. This workflow fixes communication contracts and data models early, enforcing PR sequencing and integrated validation checks to verify end-to-end behavior.

Why does parallel frontend and backend development need phase-driven orchestration?

Parallel frontend and backend development needs phase-driven orchestration to prevent contract drift and ensure alignment. It enforces phase-based collaboration, locks interfaces early, and coordinates independent components through iterative reviews and integrated validation.