stock-feature-dev

Orchestrate end-to-end Stock-Info feature development across backend, frontend, and QA teams.

Updated Oct 4, 2023
One-click install
npx skills add https://github.com/freamwork97/Stock-Info_project --skill stock-feature-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stock-feature-dev
Source: https://github.com/freamwork97/Stock-Info_project/tree/main/.agents/skills/stock-feature-dev
Command: npx skills add https://github.com/freamwork97/Stock-Info_project --skill stock-feature-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate Stock-Info feature development across backend, frontend, and QA teams to ensure end-to-end delivery.

Core Features & Use Cases

  • Orchestrates cross-team planning and execution for new features
  • Generates a shared workspace and artifacts (API specs, UI components, validation reports)
  • Supports phased workflows (requirements, implementation, testing, integration)

Quick Start

Coordinate a new feature request by stock-feature-dev to orchestrate backend, frontend, and QA teams through the end-to-end workflow.

Frequently Asked Questions about stock-feature-dev

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

FAQPage Schema
How do I coordinate full-stack feature development across backend, frontend, and QA teams?

Full-stack feature development coordination is automated by orchestrating cross-team planning and execution across backend, frontend, and QA. It generates shared workspace artifacts and enforces a phased workflow spanning requirements, implementation, testing, and integration.

What is the best way to orchestrate end-to-end workflows for new APIs and UI components?

Orchestrating end-to-end workflows for APIs and UI components is handled through a phase-based process that scaffolds a shared workspace, generates API specifications, coordinates component development, and performs integrated verification.

Can I use this to manage feature development for new pages, charts, and endpoints?

Yes, feature development for new pages, charts, APIs, and endpoints is explicitly supported. The orchestration workflow coordinates the backend-dev, frontend-dev, and qa-reviewer teams to deliver these specific request types.

How does workspace scaffolding work for cross-team feature requests?

Workspace scaffolding generates a shared workspace containing artifacts like API specs, UI components, and validation reports. This provides a unified environment for backend, frontend, and QA teams to execute within the phased workflow.

Do I need separate tools for API specification and component development during feature orchestration?

No, separate tools for API specification and component development are not needed during feature orchestration. The workflow automatically generates these workspace artifacts and coordinates their development across the required teams.

What are the limitations of using a phased workflow for feature delivery?

The phased workflow enforces a structured sequence of requirements, implementation, testing, and integration. This means feature delivery follows strict phase-based progression with workspace scaffolding and integrated verification rather than ad-hoc development.