Requirement Agent
v1.0.0需求澄清与执行确认。用于日常代码任务（修改、重构、优化、添加注释等）。当用户提出需求时，先通过快速追问（3-5 轮）完善需求，执行前根据规则判断是否需要确认。与 brainstorming（复杂系统设计）互补。
⭐ 0· 125·0 current·0 all-time
byTrackOverflow .@trackoverflow
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (clarify requirements and confirm before code edits) match the provided SKILL.md and the two configuration/reference documents. The files only define question/confirmation workflows and rules; there are no unrelated credential requests, binaries, or external dependencies.
Instruction Scope
The instructions describe asking clarifying questions (3–5 rounds) and deciding whether to auto-execute or request confirmation based on config/rules.yaml. This implicitly assumes the agent can read and modify project files (to locate files and perform edits) — which is expected for a code-modification helper, but users should be aware that the skill's behavior presumes file-system/repository access by the agent.
Install Mechanism
Instruction-only skill with no install spec and no code files that execute. Lowest installation risk: nothing is written to disk or downloaded by the skill itself.
Credentials
No required environment variables, credentials, or config paths are declared. The config files only control questioning and confirmation behavior; no sensitive tokens or unrelated service access are requested.
Persistence & Privilege
Skill flags: always=false (not force-included). disable-model-invocation=false is the platform default and appropriate here. The skill does not request persistent system-wide changes or access to other skills' configs.
Assessment
This skill appears coherent and low-risk, but it assumes the agent has permission to read and modify your codebase. Before installing: (1) ensure you want an agent that can edit repository files and that proper backups/version control are in place, (2) review and, if needed, tighten config/rules.yaml (for example require confirmation for multi-file changes, deletions, or logic changes), (3) be cautious about the 'explicit_safe' or broad 'safe_operations' that enable auto-execution, and (4) restrict the agent's file access scope in your platform so it only operates on intended projects. If you need higher assurance, request logs or a dry-run mode before allowing actual edits.Like a lobster shell, security has layers — review code before you run it.
latestvk97erf8ykteqx57jfn7n2phgd983j24z
License
MIT-0
Free to use, modify, and redistribute. No attribution required.