feature-dev

Clarify feature request unknowns and propose an MVVM implementation plan for Ledger Wallet.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Ledger-Wallet-LLC/ledgerwallet --skill feature-dev-ledger-wallet-llc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-dev
Source: https://github.com/Ledger-Wallet-LLC/ledgerwallet/tree/main/.cursor/skills/feature-dev
Command: npx skills add https://github.com/Ledger-Wallet-LLC/ledgerwallet --skill feature-dev-ledger-wallet-llc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides developers through understanding the Ledger Wallet codebase, clarifying requirements, and designing a robust feature implementation process.

Core Features & Use Cases

  • Systematic discovery: asks clarifying questions to uncover ambiguities before coding.
  • Architecture-first planning: outlines MVVM-aligned designs and integration points.
  • Incremental implementation: organizes phased work with checklists and validations.

Quick Start

Read the codebase, generate a questions list, and draft a phased implementation plan to start feature work.

Frequently Asked Questions about feature-dev

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

FAQPage Schema
How do I plan feature development for Ledger Wallet applications?▼

You plan feature development by first exploring the codebase to uncover ambiguities, generating a clarifying questions list, and drafting a phased implementation plan aligned with MVVM patterns before coding begins.

What is the best way to design MVVM architecture for a new feature?▼

Designing MVVM architecture for a new feature involves outlining integration points and creating a structured implementation plan that aligns with project rules before writing code.

How do I clarify unknowns and requirements before coding a feature?▼

Clarifying unknowns before coding involves systematically discovering ambiguities in the feature request by asking targeted questions and producing documentation artifacts prior to implementation.

Can I use this approach for incremental implementation with safety checks?▼

Yes, the approach organizes work into phased incremental implementation steps with built-in checklists and strong validation safety checks to ensure robust feature delivery.

Does feature planning require codebase exploration and documentation first?▼

Feature planning requires reading the codebase and producing documentation, questions, and artifacts first to ensure requirements are satisfied through systematic discovery and validation before execution.