plan-feature-from-issue — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited plan-feature-from-issue (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.
Convert a feature-request issue into the project's planning artifacts, keeping a clean issue → SPEC → PR(Closes #n) trace.
plan-feature router calls this when the input is a GitHub issue (or--from-issue N) that describes new product capability.
If the issue is a bug or tech-debt, stop and route it: triage-issue to classify, then plan-fix + execute-phase --fix. This skill is for genuine features only.
Per the agent guide's Workflow conventions + documentation map, then read what THIS skill needs: the feature SPEC template, the roadmap, and the issue/PR templates (.github/ISSUE_TEMPLATE/, .github/PULL_REQUEST_TEMPLATE.md) so the SPEC mirrors the fields reviewers expect. Then read the issue (forge CLI per the project's Workflow conventions — examples use gh):
gh issue view <N> --json number,title,body,labels,state,commentsdefect, regression, duplicated code, perf debt, or carries a "when to fix / trigger" clause → hand to triage-issue. State the verdict explicitly.
English), translate before drafting any artifact.
and conflicts with existing features, coupling/migration risks, and whether it should instead extend an existing feature.
needs (goals, scope in/out, architecture impact, data/schema, i18n/SEO/a11y/pricing per the docs map, a UI design reference when the feature has a UI surface, dev scenarios incl. failure modes, acceptance, dependencies, risks). For each genuine gap you can't safely default, ask the user (batch related questions; never ask what the issue or docs already answer).
XS / S / M / L (scale defined in the SPEC template)and record it in the SPEC. XS/S → the SPEC is the only planning artifact (single-pass execution); M/L → full artifact set. If L, propose splitting.
plan-feature router then runsplan-feature-scaffold for the rest of the artifact set + roadmap registration.
#N in the SPEC; the PR body must includeCloses #N so the issue closes on merge.
execute-phase.Closes #N link; an issue-born feature must close it.triage-issue — decides bug vs feature vs defer; call it if unsure.plan-fix — the fix-side sibling for bug/debt issues.plan-feature-interview (idea path); the plan-feature router picksbetween them by input.
plan-feature-scaffold — scaffolds the artifacts once the SPEC is filled.execute-phase — executes the phases; its PR carries Closes #N.#N is recorded and the PR plan includes Closes #N.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.