rcarmo/feature-refinement-flow
skel/.pi/skills/feature-refinement-flow/SKILL.md
Run a structured 20-question refinement flow before implementation for feature requests.
$ install --global
skillsauthnpx skillsauth add rcarmo/piclaw feature-refinement-flowInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 11, 2026, 8:34 PM14.2s1 file scanned
SKILL.md
- name:
- feature-refinement-flow
- description:
- Run a structured 20-question refinement flow before implementation for feature requests.
- distribution:
- public
Feature Refinement Flow
Use this skill to turn a feature request into a clear, implementation-ready work item.
When to use
Invoke when a request includes:
- behavior changes,
- new integrations,
- UI/editor workflow changes,
- or non-trivial architectural decisions.
Goal
Turn vague ideas into:
- A concrete user outcome
- A deterministic implementation scope
- A reproducible test plan
Default process
Ask up to 20 questions in sequence, one-at-a-time, unless already answered.
20-question baseline
- What is the problem statement and why does it matter now?
- Who is the primary user and what workflow do they follow today?
- What are the success criteria (observable outcomes)?
- What is the MVP behavior (minimum useful version)?
- What is explicitly out of scope?
- Which files/surfaces are in scope (frontend, backend, extension API, tests)?
- Any required platform constraints (browser support, runtime limits, auth mode)?
- What should happen on error/failure cases?
- What is required for data persistence / storage semantics?
- Which existing pattern should this align with?
- What should be changed first (lowest-risk slice)?
- What should we avoid for v1?
- How should file types, formats, and naming be handled?
- Who/what are the inputs and outputs of this feature?
- What should happen to existing behavior during this change?
- What are the expected performance and startup/load constraints?
- What security / permissions concerns apply?
- What should be exportable / shareable and in which format(s)?
- How will we prove this works (test plan)?
- What is the acceptance/closure condition for “done”?
How to use in work items
- Add a short “Refinement notes” section in the work item with the 20-question answers.
- Convert answers into:
- acceptance criteria,
- risks,
- implementation path,
- test plan,
- definition of done.
- Add blockers only where known (uncertain candidate APIs, policy issues, missing assets).
Preference persistence
Keep answers in a feature-scoped notes/work-item file or notes/preferences/feature-refinement.md if the process becomes reusable.
Practical tip
Prefer narrow first, iterate later: lock scope by answering 1–10 first, then expand with dependency/testing details only after behavior is clear.
Related Skills
rcarmo/m365-document-link-metadata
documentation
VerifiedTrustedCommunity
Resolve Teams or SharePoint document links to canonical metadata.
511SKILL.mdUpdated Apr 15, 2026
rcarmo/web-search
development
VerifiedTrustedCommunity
Search the web via SearXNG and optionally convert result pages to Markdown.
468SKILL.mdUpdated Apr 11, 2026
rcarmo/web-search-summary
development
VerifiedTrustedCommunity
Search via SearXNG, fetch top results, and return quick summaries plus markdown.
468SKILL.mdUpdated Apr 11, 2026
rcarmo/twitter-summary
testing
VerifiedTrustedCommunity
Fetch a user's recent tweets (tweets, replies, retweets) using Playwright + Nitter fallbacks and produce compact JSON/Markdown summaries.
468SKILL.mdUpdated Apr 11, 2026