workflow-feature-spec — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited workflow-feature-spec (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
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.
Pipeline that takes a fuzzy feature idea and ends with an executable implementation plan grounded in business intent + technical spec.
superpowers:brainstorming directly.superpowers:writing-plans directly.| Step name | Stage | Invokes |
|---|---|---|
brief | Business context | biz-brief |
spec | Technical spec | superpowers:brainstorming |
plan | Implementation plan | superpowers:writing-plans |
brief — invokes biz-briefGenerates a 1-page Business Context Brief and saves it to docs/superpowers/briefs/YYYY-MM-DD-<feature>.md.
Output: brief file exists. Checkpoint: confirm brief is accurate before brainstorming.
spec — invokes superpowers:brainstormingBrainstorms the technical spec with the brief loaded as context. Saves spec to docs/superpowers/specs/YYYY-MM-DD-<feature>.md.
Output: spec file exists. Checkpoint: confirm spec coverage before writing the plan.
plan — invokes superpowers:writing-plansReads the spec and produces a task-by-task plan at docs/superpowers/plans/YYYY-MM-DD-<feature>.md.
Output: plan file exists, ready to hand off to subagent-driven-development or executing-plans.
Default: run brief → spec → plan in order, with checkpoints between each.
--resume-from <step>: skip every step before <step> and begin from <step>. The named step itself runs.
If <step> is not in {brief, spec, plan}, print:
Invalid resume-from step: <step> Valid steps: brief, spec, plan
…and stop.
Before running the resume step, confirm the listed inputs exist. If anything is missing, prompt the user for it.
--resume-from brief — same as a fresh run; needs only the feature name.--resume-from spec — needs the brief at docs/superpowers/briefs/YYYY-MM-DD-<feature>.md. If absent, ask the user to paste it or run from brief. Brainstorming loads the brief as context.--resume-from plan — needs the spec at docs/superpowers/specs/YYYY-MM-DD-<feature>.md. If absent, ask the user to paste it or run from spec. Writing-plans operates on the spec.Examples:
/workflow-feature-spec --resume-from spec # brief already exists, brainstorm from it /workflow-feature-spec --resume-from plan # spec is approved, just write the plan
--no-pause to run end-to-end (rare — usually you want the checkpoints here).Brainstorming and writing-plans both have their own surface-assumptions / push-back behaviors built in. The workflow does not paper over those — when a sub-skill asks a clarifying question, the workflow surfaces it to the user. If a stage errors, stop and print the failed step plus the resume command (/workflow-feature-spec --resume-from <step>).
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.