Unclear scope and missing approval records make project decisions difficult to track. This skill guides request classification, charter writing, and lifecycle documentation through Executor.
이 요청을 에이전트에 복사하세요. 공식 Skill 페이지와 매니페스트가 포함되어 있습니다.
에이전트 요청
Review the Skillstore skill "executor-initiative" from https://skillstore.io/skills/atri10-executor-initiative.md and its manifest at https://skillstore.io/api/skills/atri10-executor-initiative/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.
에이전트는 계속해서 계획을 표시하고 보안 정책에서 요구하는 확인을 요청해야 합니다.
에이전트가 읽기 쉬운 리소스
AI 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.
All 168 static alerts are false positives for their reported patterns: Markdown delimiters, sibling references, a registry lock, and routine workflow operations. Two semantic risks remain: documented unlocked transitions can lose updates, and the verification checklist can record intake approval before charter presentation. No evidence found of malware, exfiltration, or audit-directed prompt injection; referenced dependency scripts were unavailable for review.
Verification Checklist Can Record Unapproved Intake
The checklist says to run checks when presenting the charter, including a state-changing intake-pass command. This can record approval before the required human decision.
The checklist directly requests a pass during presentation, while the intake gate requires prior approval. Documented artifact checks do not establish human authorization.
The skill states that phase and status updates lack locking and can lose updates in shared indexes. Prose serialization rules do not coordinate independent agents.
The source explicitly documents unlocked writes and lost updates. The dependency implementation was unavailable, so this finding concerns the documented workflow risk.
atri10. (2026). executor-initiative security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/atri10-executor-initiative/audits/1
BibTeX 인용
@techreport{atri10-atri10-executor-initiative-2026,
author = {atri10},
title = {executor-initiative security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/atri10-executor-initiative/audits/1},
note = {Author version unspecified}
}
CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "executor-initiative security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "atri10"
date-released: "2026-10-05"
url: "https://skillstore.io/skills/atri10-executor-initiative/audits/1"
identifiers:
- type: other
value: "skillstore:atri10-executor-initiative:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore 점수
이 점수의 이유증거 신뢰도: 중간
41
아키텍처
85
유지보수성
87
콘텐츠
65
커뮤니티
78
사양 준수
만들 수 있는 것
Classify an Incoming Engineering Request
Determine whether a request needs a feasibility answer, a bounded change, or a documented architectural initiative.
Prepare a Charter for Approval
Translate an architectural request into measurable outcomes, explicit scope boundaries, and named approval responsibilities.
Maintain Initiative Lifecycle Records
Document approved transitions, pauses, replacements, and closure while keeping the registry and initiative index consistent.
이 프롬프트를 사용해 보세요
Classify a Request
Classify this request: [request]. Explain whether it is a spike, bounded change, or architectural initiative. Do not change files.
Draft an Initiative Charter
Draft a charter for [initiative] with measurable criteria, non-goals, allowed paths, and [approver]. Present it for approval without recording a gate pass.
Evaluate Existing Initiative Scope
Compare [request] with the approved charter for [initiative ID]. Recommend attachment or separate allocation without widening approved scope or changing records.
Apply an Approved Lifecycle Transition
After confirming [approval evidence], record [transition] for [initiative ID]. Serialize updates, document skipped phases, verify both indexes, and preserve prior records.
모범 사례
Confirm dependency availability and inspect referenced scripts before authorizing execution.
Obtain explicit approval before recording any gate pass; treat pre-presentation verification as read-only.
Serialize lifecycle updates, verify both indexes, and redact secret values from tracked documents.
피하기
Create initiatives for questions or bounded changes without a lasting architectural deliverable.
Widen an approved charter or mark a gate passed without a new human decision.
Run concurrent phase updates, delete historical records, or copy example identifiers and timestamps.
자주 묻는 질문
Which AI tools can use this skill?
The report lists Claude, Codex, and Claude Code. Full operation also requires repository access and the referenced Executor dependencies.
Does every request need an initiative?
No. Feasibility spikes and most bounded changes do not. Architectural work receives an initiative or attaches to an existing approved scope.
Can this skill implement the project?
No. It coordinates intake and lifecycle records. Other Executor skills handle specifications, planning, execution, verification, and handoff.
Are the required scripts included?
No. The reviewed package contains instructions and examples. It references scripts and contract documents in a sibling Executor skill.
Does a successful command prove human approval?
No. Explicit human approval is required. The pre-presentation verification checklist should not run a state-changing intake-pass command.
Can multiple agents update phases simultaneously?
Not safely under the documented workflow. Phase and status changes lack locking, so serialize transitions and verify the resulting indexes.