plan-feature-interview — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited plan-feature-interview (Agent Skill) and scored it 96/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 1 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 1 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Turn a rough idea into a well-scoped, architecture-respecting feature through a focused interview. Optimizes for catching unknowns before implementation.
plan-feature router calls this when the input is a vague idea (or the userforces it with --interview) and wants help thinking it through before any code.
Per the agent guide's Workflow conventions + documentation map, then read what THIS skill needs: the architecture doc, the domain/style docs relevant to the idea's area, the SPEC template, and the roadmap. Goal: ask only what the project does not already answer, and ground every question in the project's real constraints (layering, domain/i18n/SEO/a11y rules, runtime/platform limits, naming conventions).
problem it solves and for whom. Get a yes/adjust before going deeper.
batched rounds (use the question tool; group related questions; offer a recommended default each). Skip anything the docs already settle.
adapters; honor the dependency rules.
map. Call out which apply.
design to build against (design-system components, mockup, Figma)? If the surface is significant and no reference exists, flag that a design pass should precede implementation rather than letting the code improvise.
races, outages) and how to reproduce each locally.
XS / S / M / L (the SPEC template defines the scale).XS/S → SPEC-only, single-pass execution; M/L → full artifact set, phased. If L, propose splitting into independently shippable features.
didn't mention; flag conflicts with existing architecture or docs; propose the smallest version that delivers the value.
template); if created, the PR will Closes #n.
plan-feature router then runs plan-feature-scaffold for the remaining artifacts + roadmap registration.
execute-phase.
synthesize.
open questions in decisions.md rather than blocking.
plan-feature-from-issue (issue path); the plan-feature routerpicks between them by input.
plan-feature-scaffold — scaffolds the artifacts once the interview yields a SPEC.execute-phase — executes the phases afterward.question), a filled SPEC + artifacts exist, and the user knows the next step.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.