impl-fe-be-doc

Generate structured implementation roadmaps for full-stack web applications.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/hb9397/ai-agent-harness-docs --skill impl-fe-be-doc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: impl-fe-be-doc
Source: https://github.com/hb9397/ai-agent-harness-docs/tree/main/plugins/ai-agent-harness/runtime/claude/skills/impl-fe-be-doc
Command: npx skills add https://github.com/hb9397/ai-agent-harness-docs --skill impl-fe-be-doc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the ambiguity in full-stack development by bridging the gap between high-level design documents and granular, actionable implementation tasks for both frontend and backend teams.

Core Features & Use Cases

  • Phase-based Planning: Automatically breaks down complex features into independent, testable phases with clear dependencies.
  • FE/BE Integration: Maps frontend components and state management to corresponding backend API endpoints and database models.
  • Use Case: When starting a new feature like a checkout flow, use this skill to generate a detailed roadmap that ensures the backend API, database schema, and frontend UI components are developed in the correct, verifiable order.

Quick Start

Use the impl-fe-be-doc skill to generate a full-stack implementation plan based on the provided design document.

Frequently Asked Questions about impl-fe-be-doc

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

FAQPage Schema
How do I generate a full-stack implementation roadmap from a design document?

To generate a full-stack implementation roadmap, provide your design document to break down complex features into independent, testable phases with clear dependencies. This coordinates frontend components, backend API endpoints, and database models into sequential development tasks.

What is the best way to map frontend components to backend API endpoints?

Mapping frontend components to backend API endpoints involves coordinating state management with corresponding backend endpoints and database models. This process enforces standardized task IDs and integration verification scenarios to ensure technical alignment between FE and BE teams.

How do I break down a complex web feature into sequential development phases?

Breaking down a complex web feature requires phase-based planning that generates independent, testable phases with clear dependencies. It maps frontend UI components, backend API endpoints, and database integration into a verifiable development order for teams.

Can I use this to plan database integration alongside frontend state management?

Yes, you can plan database integration alongside frontend state management. The task specification coordinates database models with frontend components and backend APIs, ensuring standardized task IDs and dependency tracking across the full-stack web application.

Does this approach enforce dependency tracking between frontend and backend tasks?

Yes, this approach enforces dependency tracking between frontend and backend tasks. It assigns standardized task IDs and creates integration verification scenarios, ensuring technical alignment and correct development order across FE and BE teams.