feature-dev

Document end-to-end feature development workflows across discovery, design, implementation, and testing.

3|Updated Apr 30, 2024
One-click install
npx skills add https://github.com/LiamMarega/astro-portolio --skill feature-dev-liammarega
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-dev
Source: https://github.com/LiamMarega/astro-portolio/tree/main/.agents/skills/feature-dev
Command: npx skills add https://github.com/LiamMarega/astro-portolio --skill feature-dev-liammarega

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill provides a structured, iterative approach to delivering features by deeply understanding the codebase, clarifying ambiguities, designing robust architectures, implementing code, and validating with tests and reviews.

Core Features & Use Cases

  • Phase-driven workflow: discovery, exploration, clarification, architecture design, implementation, testing, quality review, and summary.
  • Todo-driven collaboration: creates a plan, tracks decisions, and aligns team members across phases.
  • Risk-aware decisions: prompts for questions and verifications to reduce miscommunications and rework.

Quick Start

Announce at the start that you are using the feature-dev skill to implement this feature.

Frequently Asked Questions about feature-dev

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

FAQPage Schema
What is a systematic end-to-end workflow for feature development?

Systematic feature development integrates discovery, codebase exploration, architecture design, implementation, testing, and quality review. It resolves ambiguities through clarifying questions and tracks progress using todo management to ensure repeatable, traceable delivery.

How do I plan architecture design and implementation for a new feature?

Architecture design and implementation planning begin with deep codebase exploration and asking clarifying questions. This phase defines requirements for guardrails and validation, creating a todo-driven plan that aligns team members and reduces rework.

How do you manage code review and testing in an iterative feature workflow?

Code review and testing in an iterative workflow are managed through a phased approach validating implementation against designed guardrails. Todo-driven progress tracking ensures decisions are documented and quality review is repeatable.

Can I use todo-driven progress tracking for complex codebase understanding tasks?

Todo-driven progress tracking effectively manages complex codebase understanding by breaking exploration and implementation into traceable steps. It documents decisions and aligns team members across all feature development phases.

What is the best way to resolve ambiguities before architecture design in software engineering?

The best way to resolve ambiguities before architecture design is applying a structured workflow that prompts clarifying questions during codebase exploration. This risk-aware approach verifies details to reduce miscommunications and rework.

Does feature development require predefined guardrails and validation requirements?

Feature development requires predefined guardrails and validation requirements to ensure robust architecture design and quality review. Establishing these early prevents errors during implementation and testing.