Security audit
Security checks for vulnerabilities and agentic risk
This skill is a bounded problem-discovery aid with a small local guide-generation script and no evidence of hidden access, network use, persistence, or destructive behavior.
Before installing, note that the skill is intended for discovery documents and interview guides, not PRDs or implementation plans. Review outputs for accidental solution commitments, especially when using the requirement-analysis reference, and choose output paths carefully because the helper script will write to the path you provide.
Referenced artifact was not completely inspected
To generate consistent interview guides for several roles, run `node scripts/generate-interview-guide.js --input project.json --output interview-guide.md`. The
The Y-model section moves from identifying user needs and motivations to reconstructing a better product solution, directly conflicting with the skill boundary against committing to solutions. In an agent skill, this can cause the model to bypass discovery discipline and prematurely recommend designs, creating unsafe or out-of-scope behavior.
Advising verification through MVPs or grayscale releases crosses from research into experimentation and proto-solution deployment, which the manifest explicitly forbids. In practice, this can push an agent to recommend building or shipping test implementations rather than staying within analysis and validation boundaries.
Stating that the output can be directly used as PRD input encourages use of this discovery artifact as a bridge into solution-definition work, contrary to the manifest. In the skill context, this makes the issue more dangerous because the agent is likely to treat the document as permission to produce forbidden PRD content.
The document explicitly frames itself as pre-analysis before writing a PRD, which exceeds the skill's declared problem-discovery-only scope. This creates scope drift: an agent using this reference could start producing downstream product-definition artifacts despite instructions not to commit to solutions or write PRDs.
Including implementation-oriented 'How' guidance introduces design and engineering considerations into a discovery-only workflow. That increases the chance an agent will generate architecture or delivery recommendations before the problem has been validated, undermining the skill's intended safeguards.
Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
The template renders role headings using full-width parentheses characters, which imposes a locale-specific output format. Under the policy rule, language or locale constraints should not be forced without user opt-in unless clearly justified.
This code performs a filesystem write via fs.writeFileSync, which is a safety-relevant operation under the review rules. While the CLI requires an explicit --output path, there is no confirmation prompt, overwrite warning, or inline documentation disclosing that the specified file will be created or replaced.
No suspicious patterns detected.