feature-spec
Build a non-ambiguous, complete, provenance-tagged product spec for a feature area — the behavioral oracle that prove-behavior tests against. Researches every reachable source (code, live product, sibling specs, Jira, Confluence, Slack, git history) to build a mental map, then interrogates the user exhaustively to resolve EVERY ambiguity before writing. Use when: (1) user says 'feature-spec', 'write the spec for X', 'build the product spec', 'spec out this feature', (2) before running prove-behavior on a feature that has no spec yet, (3) onboarding onto a feature and wanting the ground-truth contract. One spec per feature AREA (e.g. all of the settings screen, or checkout, or the text editor). Output: docs/features/<area>/product-spec.md.
73
90%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Low
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
The required workflow uses research agents that read Jira and Confluence tickets to build a feature spec, which exposes the agent to outsider-authored free text.
- Repository
- mayank-arora/agent-skills
- Commit
d58ca85
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.