feature-implement

Orchestrate sequential UserStory implementations and lifecycle transitions for software features.

19|3|Updated Jul 19, 2024
One-click install
npx skills add https://github.com/danielterra/FOUNDATION --skill feature-implement-danielterra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-implement
Source: https://github.com/danielterra/FOUNDATION/tree/main/.claude/skills/feature-implement
Command: npx skills add https://github.com/danielterra/FOUNDATION --skill feature-implement-danielterra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates end-to-end software feature delivery by coordinating all planned SoftwareFeature implementations through child UserStories using /userstory-implement and guiding user validation before final delivery.

Core Features & Use Cases

  • Orchestrates sequential implementation of all eligible child UserStories via /userstory-implement.
  • Validates build outcomes and moves UserStories to Testing, advances Feature status through the lifecycle, and updates the changelog.
  • Handles failure by pausing the flow and prompting user decisions, ensuring safe rollback if needed.

Quick Start

Feed the Feature IRI and let the skill orchestrate all child UserStories with /userstory-implement, then guide validation and lifecycle transitions to Testing.

Frequently Asked Questions about feature-implement

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

FAQPage Schema
How do I orchestrate end-to-end feature implementation for planned user stories?

Feature implementation is orchestrated by sequentially coordinating all planned child UserStories through /userstory-implement, validating builds, and transitioning the Feature lifecycle from Planned to InProgress and Testing.

What is the process for moving a software feature from Planned to Testing status?

Moving a Feature to Testing requires sequentially implementing all child UserStories, validating build outcomes via cargo check/build, and updating the Feature status while appending a changelog entry using add_property_values.

How does build validation work during user story implementation?

Build validation runs cargo check/build through /userstory-implement for each UserStory. If validation fails, the orchestration pauses the flow and prompts user decisions to ensure a safe rollback if needed.

Do I need my child UserStories already planned before starting feature lifecycle management?

Yes, this Skill is applicable only when a Feature has its child UserStories already planned. It orchestrates their sequential implementation and guides user validation before final delivery.

Can I execute multiple user stories in parallel during feature delivery?

No, the orchestration enforces sequential execution of all eligible child UserStories. It processes each one individually via /userstory-implement before advancing the overall Feature lifecycle.

What happens if a build fails during sequential user story implementation?

When a build fails, the orchestration pauses the workflow and prompts user decisions. This mechanism ensures safe rollback and prevents advancing the Feature lifecycle until the issue is resolved.