Drafts and iterates structured feature request markdown files as a staff-level Product Manager.
npx skills add https://github.com/FHIR/fhir-codegen --skill dev-request-fhir
Please help me install this Agent Skill. Skill: dev-request Source: https://github.com/FHIR/fhir-codegen/tree/main/.github/skills/dev-request Command: npx skills add https://github.com/FHIR/fhir-codegen --skill dev-request-fhir
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 new featurerequest.md from a raw idea, transcript, or bullet list, resolving targets by full path or a numeric slot that expands to scratch/<MMDD>-<##>/featurerequest.md. - Iteration & Review: Reads an existing request, preserves untouched sections, and revises based on new feedback without silently dropping content. - GitHub Issue Seeding: Optionally fetches an existing issue via gh issue view to seed the draft title, problem, and notes. - Open Questions Walkthrough: Offers an interactive one-question-at-a-time walkthrough with recommended answers and rationales, applying each answer to the document. - Use Case: You have a one-line idea for a new CLI flag. Invoke the skill with slot 2 and your idea; it writes a complete proposal under scratch/, flags assumptions, and walks you through unresolved scope questions. ## Quick Start Ask the AI to draft a feature request for slot 3 describing your idea, for example: create a feature request in slot 3 for adding JSON output to the codegen CLI.High-intent search queries and answers about installing and using this skill.
Invoke the skill with a target path or slot number plus your raw idea. It writes a featurerequest.md with Problem, Goals, Non-Goals, Users, Open Questions, and Assumptions sections, marking anything uncertain as an explicit assumption.
Pass the issue as #N, gh#N, or a full issue URL along with your target. The skill fetches it with gh issue view and seeds the heading, Problem section, and Notes, while still applying PM judgment rather than pasting the issue verbatim.
Yes. When the resolved file already exists, the skill reads it and revises based on your new input, preserving sections you did not ask to change. If it must remove something, it mentions the removal in its reply.
Files live under scratch/<MMDD>-<##>/featurerequest.md when you give a slot number, or at any full path you provide. The scratch directory is gitignored, so drafts are never committed.
The skill offers an interactive walkthrough, asking one question at a time with at most three concrete answers, one recommendation, and a free-form option. Each answer is applied to the document before moving to the next question.
Do not use it for implementation plans, bug reports, or code reviews. Those belong to the paired dev-plan, dev-report, and dev-review skills; this skill stays in the PM role and describes problems, not solutions.
rbutinarCapture structured user feedback and submit it via commit or GitHub Issue.
ContentsUSExecute implementation plans from GitHub issues into pull requests.
mmdmcyGuides building and comparing multiple prototypes before committing to novel design decisions.
i-am-beeDraft GitHub issues for i-am-bee/agentstack with templates and labels.