Guided Development Skill

Guide incremental feature implementation through PRD-first task decomposition.

75|8|Updated Dec 20, 2023
One-click install
npx skills add https://github.com/flowkraft/datapallas --skill guided-development-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Guided Development Skill
Source: https://github.com/flowkraft/datapallas/tree/main/asbl/src/main/external-resources/db-template/_apps/flowkraft/_ai-hub/.skills/guided-development
Command: npx skills add https://github.com/flowkraft/datapallas --skill guided-development-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps users successfully implement features by breaking work into clear, testable tasks while staying in the driver’s seat and learning the codebase as they go.

Core Features & Use Cases

  • Mentored pair-development workflow: explains the approach, provides focused snippets, and directs where changes should go so the user integrates and tests.
  • PRD-first delivery: checks for an existing product requirements document (in /docs/product/) and creates one when missing to align on goals and acceptance criteria.
  • Task decomposition with traceability: converts requirements into a numbered implementation task list (optionally including a PlantUML WBS diagram) and proceeds task-by-task.
  • Practical integration strategy: guides Phase 0 by building on an existing playground project integrated with DataPallas lifecycle (build/start/stop), then removing demo artifacts only after the custom features work.

Quick Start

Tell the skill what feature you want to build and where your integrated playground project lives, and it will guide you to create or reuse the PRD and start the first numbered implementation task.

Frequently Asked Questions about Guided Development Skill

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

FAQPage Schema
How do I break feature requirements into small testable tasks for an existing codebase?

Task decomposition converts product requirements into a numbered implementation list, optionally using a PlantUML WBS diagram, and proceeds task-by-task to ensure safe, incremental feature delivery.

How does a PRD-first workflow guide pair programming and feature implementation?

A PRD-first workflow checks for an existing product requirements document in the docs product folder and creates one if missing to align goals and acceptance criteria before guided development begins.

What is the best way to integrate new features into a playground project before removing demo artifacts?

Phase 0 integration builds on an existing playground project integrated with the DataPallas lifecycle, executing build, start, and stop commands, then removing demo artifacts only after custom features work.

Do I need a product requirements document before starting mentored pair-development?

Yes, mentored pair-development requires a product requirements document to align on explicit file placement, focused code snippets, and iterative user-driven integration and testing.

Can I use this guided development approach if my codebase lacks a playground project?

The practical integration strategy requires an existing playground project integrated with the DataPallas lifecycle to guide Phase 0 builds before safely removing demo artifacts.

Why does task-by-task integration require iterative user-driven testing during development?

Iterative user-driven testing ensures the user stays in the driver seat, integrating focused code snippets and debugging incrementally until all acceptance criteria are met.