feature

Orchestrate end-to-end feature pipelines from planning to release artifacts.

11|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/satanyakiv/NutriSport --skill feature-satanyakiv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature
Source: https://github.com/satanyakiv/NutriSport/tree/main/.claude/skills/feature
Command: npx skills add https://github.com/satanyakiv/NutriSport --skill feature-satanyakiv

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

NutriSport teams spend significant time stitching together design, scaffolding, navigation wiring, and test scaffolds for new features. This Skill automates the end-to-end feature pipeline to coordinate planning, per-screen interleaving, and quality gates into a single workflow.

Core Features & Use Cases

  • End-to-end feature pipeline from plan to ship for multi-screen flows.
  • Interactive plan-mode before execution, per-screen interleaving, and visual fidelity checks.
  • Auto-wiring of navigation, DI modules, and tests; produces a final commit with a gates report.

Quick Start

Provide a feature plan and Figma frames to start Phase A and begin the interactive plan mode.

Frequently Asked Questions about feature

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

FAQPage Schema
How do I automate end-to-end feature pipeline orchestration from plan to ship?

End-to-end feature pipeline orchestration automates interactive planning, per-screen scaffolding, Figma handoffs, UI verification, testing, and release artifacts into a single workflow. You provide a feature plan and Figma frames to begin interactive plan mode before execution.

How does Figma integration work for multi-screen feature scaffolding?

Figma integration works through per-frame handoffs during the feature pipeline, extracting design specs to drive code scaffolding and visual fidelity checks. The pipeline interleaves per-screen scaffolding with Figma data to ensure UI verification before release.

Can I use this feature pipeline for multi-screen flows in NutriSport and similar projects?

Yes, the feature pipeline is explicitly designed for multi-screen flows in NutriSport and similar projects. It handles frontmatter-driven planning, per-frame Figma integration, navigation wiring, and tests to produce a final commit with a complete gates report.

What is the best way to wire navigation and DI modules during feature development?

The best way to wire navigation and DI modules is using the feature pipeline's auto-wiring capabilities during per-screen scaffolding. It automatically configures navigation, DI modules, and test scaffolds, concluding with a final commit and a gates report.

Do I need a feature plan and Figma frames to start the pipeline?

Yes, you need to provide a feature plan and Figma frames to start Phase A and begin the interactive plan mode. These inputs are required to initiate the frontmatter-driven planning and per-frame Figma integration processes.

What are the limitations of automating feature development with interactive planning?

The feature pipeline requires structured frontmatter-driven planning inputs and Figma frames to function correctly. It is specialized for multi-screen flows and relies on completing interactive plan mode before execution can proceed to scaffolding and testing.