dev-request

Drafts and iterates structured feature request documents as a staff-level Product Manager.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/GinoCanessa/dotnet-fhir-packages --skill dev-request-ginocanessa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-request
Source: https://github.com/GinoCanessa/dotnet-fhir-packages/tree/main/.github/skills/dev-request
Command: npx skills add https://github.com/GinoCanessa/dotnet-fhir-packages --skill dev-request-ginocanessa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough feature idea into a reviewable proposal takes PM discipline most developers skip. This Skill captures feature requests as structured featurerequest.md files with problem statements, goals, non-goals, open questions, and assumptions, so a tech lead can take them straight to planning. ## Core Features & Use Cases - Structured drafting: Creates a featurerequest.md with Problem, Goals, Non-Goals, Users/Callers, UX sketch, Open Questions, Assumptions, and Notes sections. - Iteration and review: Reads an existing request, preserves untouched sections, and revises based on new input without silently dropping content. - GitHub issue seeding: Optionally fetches an existing issue via gh issue view to seed the draft, with slot-number or full-path targeting under scratch/. - Open Questions walkthrough: Offers an interactive one-question-at-a-time pass with recommended answers and rationales, then hands off to dev-approach, dev-plan, or dev-issue when status reaches Ready-for-plan. - Use Case: You have a one-line idea for a new CLI flag. Invoke the skill with slot 2 and your idea; it writes scratch/<MMDD>-02/featurerequest.md as a full proposal and walks you through the unresolved questions. ## Quick Start Ask the assistant to draft a feature request for slot 2 describing your idea, for example: "Use dev-request on slot 2 to capture a request for JSON output on the list command."

Frequently Asked Questions about dev-request

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

FAQPage Schema
How do I turn a feature idea into a structured feature request document?

Invoke the skill with a target slot number or file path plus your raw idea. It writes a featurerequest.md with Problem, Goals, Non-Goals, Users, a non-binding UX sketch, Open Questions, and Assumptions, then reports a summary back.

How do I draft a feature request from an existing GitHub issue?

Pass the issue as #N, gh#N, or a full issue URL along with your target. The skill fetches it with gh issue view, seeds the title and body into the draft, and records labels and URL in Notes. A failed fetch is not a blocker.

Can I iterate on an existing feature request without losing content?

Yes. When the target file already exists, the skill reads it, applies your new input, and preserves sections you did not ask to change. Removed content is always mentioned in the reply rather than silently dropped.

Where are feature request files stored and are they committed?

Files live under scratch/<MMDD>-<##>/featurerequest.md, where the date is today's local date and the slot is zero-padded. The scratch directory is gitignored, so requests are never committed.

What happens after a feature request reaches Ready-for-plan status?

The skill offers a hand-off to dev-approach for competing solution shapes, and optionally to dev-issue for publishing to GitHub when the integration is enabled. Declining either offer is fully supported.