Compétences executor-planning
đŠ
executor-planning
RĂ©vision du contenu r1 Risque moyen âïž Commandes externesđ AccĂšs au systĂšme de fichiers
Turn Approved Specifications into Implementation Plans
Incomplete implementation plans leave developers guessing about interfaces, dependencies, and acceptance criteria. This skill structures approved specifications into traceable tasks with explicit tests and execution gates.
Prend en charge: Claude Codex Code(CC)
Installer avec mon Agent
Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.
Demande dâagent
Review the Skillstore skill "executor-planning" from https://skillstore.io/skills/atri10-executor-planning.md and its manifest at https://skillstore.io/api/skills/atri10-executor-planning/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.
Ressources lisibles par les agents
Utilisez ces liens lorsquâun Agent IA, un crawler ou un script a besoin dâun contexte propre au lieu de lire toute la page.
Tester
Utilisation de « executor-planning ». Plan an approved feature that adds scoring and routing through documented interfaces.
RĂ©sultat attendu:
- Draft plan: scoring and routing, with requirement coverage and exact interface contracts.
- Task sequence: define shared types, implement scoring, then integrate routing.
- Dependency map: routing consumes shared types and scoring results.
- Acceptance checks: explicit expected values, negative-input tests, and repeatable test commands.
- Handoff: complete plan regression before asking the human to select an execution mode.
Utilisation de « executor-planning ». Review a draft plan whose final task contains a dependency section and omits an expected test failure.
RĂ©sultat attendu:
- Extraction defect: move the dependency section above the first task heading.
- Test defect: name the exact expected failure before implementation exists.
- Coverage check: associate every requirement with at least one task.
- Verification status: rerun task extraction and plan linting with the companion tools before claiming the gate passed.
Audit de sécurité
Risque moyenv1 ⹠05/10/2026 Ouvrir le rapport versionné
Most of the 221 static findings are Markdown formatting, legitimate companion references, or routine planning commands. Two temporary-file findings remain confirmed, and a semantic finding identifies overly broad Git staging. No evidence found of prompt injection or exfiltration; companion script implementations are outside the reviewed package.
1
Fichiers analysés
773
Lignes analysées
2
ĂlĂ©ments Ă examiner
0
Faux positifs ignorés
Préoccupations de sécurité confirmées (1)
Moyen
Broad Git Staging Can Include Unrelated Changes
The handoff runs 'git add docs/executor/INIT-0004-cloud-tenant-cells' before committing. Directory-wide staging can include unrelated or sensitive initiative files beyond the intended plan, index, and specification updates.
The example explicitly stages the entire initiative directory instead of the three intended document updates. Actual exposure depends on other changes in that directory.
ĂlĂ©ments dâĂ©valuation des capacitĂ©s (2)
Il sâagit de capacitĂ©s locales rĂ©elles qui peuvent ĂȘtre attendues pour cette compĂ©tence ; elles nĂ©cessitent donc un examen, mais ne sont pas comptabilisĂ©es comme comportement malveillant confirmĂ©.
Moyen
Temp directory access
"$n" /tmp/brief-check.md >/dev/null || echo "TASK $n FAILS"
The example writes each brief to a predictable shared temporary pathname without showing exclusive creation. Concurrent runs or precreated links could corrupt or redirect output.
Moyen
Temp directory access
grep -m1 '^\*\*Task:\*\*' /tmp/brief-check.md
The loop reads the same shared temporary file even after extraction failure. Stale output or another concurrent run could substitute the task identity being verified.
Facteurs de risque
âïž Commandes externes (50)
SKILL.md:8 SKILL.md:21 SKILL.md:31 SKILL.md:32 SKILL.md:33 SKILL.md:34 SKILL.md:35 SKILL.md:36 SKILL.md:37 SKILL.md:39 SKILL.md:40 SKILL.md:41 SKILL.md:42 SKILL.md:44-45 SKILL.md:46 SKILL.md:47 SKILL.md:49 SKILL.md:54 SKILL.md:56 SKILL.md:65 SKILL.md:66 SKILL.md:68 SKILL.md:69 SKILL.md:70 SKILL.md:75 SKILL.md:76 SKILL.md:77 SKILL.md:79-83 SKILL.md:83-85 SKILL.md:85 SKILL.md:86 SKILL.md:88-93 SKILL.md:93-95 SKILL.md:95-96 SKILL.md:96-101 SKILL.md:101 SKILL.md:113-116 SKILL.md:116-119 SKILL.md:119-121 SKILL.md:121 SKILL.md:122 SKILL.md:126-128 SKILL.md:128 SKILL.md:129-132 SKILL.md:132-167 SKILL.md:167-169 SKILL.md:169 SKILL.md:176 SKILL.md:177 SKILL.md:190-193
đ AccĂšs au systĂšme de fichiers (21)
Audité par: codex
Partager et citer ce rapport
Partagez le rapport dâĂ©valuation versionnĂ©, le badge neutre, la carte intĂ©grable et les citations. Skillstore prĂ©sente les preuves sans dĂ©cider si ce Skill est sĂ»r.
Copier le lien du rapport
https://skillstore.io/skills/atri10-executor-planning/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportBadge Markdown
[](https://skillstore.io/skills/atri10-executor-planning?utm_source=security_passport_badge)Badge HTML
<a href="https://skillstore.io/skills/atri10-executor-planning?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/atri10-executor-planning/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Carte intégrable
<iframe src="https://skillstore.io/embed/skills/atri10-executor-planning.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Citations académiques (APA · BibTeX · CFF)
Citation APA
atri10. (2026). executor-planning security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/atri10-executor-planning/audits/1Citation BibTeX
@techreport{atri10-atri10-executor-planning-2026,
author = {atri10},
title = {executor-planning security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/atri10-executor-planning/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-planning 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-planning/audits/1"
identifiers:
- type: other
value: "skillstore:atri10-executor-planning:audit:1"
description: "Skillstore immutable audit report identifier"
Score Skillstore
Pourquoi ce score Niveau de confiance des preuves: Moyen 55
Architecture
85
Maintenabilité
87
Contenu
65
Communauté
74
Conformité aux spécifications
Ce que vous pouvez créer
Prepare a Reviewable Delivery Plan
Convert an approved feature specification into traceable tasks with explicit file ownership, interfaces, and acceptance tests.
Create Self-Contained Agent Briefs
Prepare tasks that isolated coding agents can implement without access to the surrounding conversation or complete plan.
Repair a Multi-Plan Handoff
Find missing requirement coverage, interface mismatches, dependency cycles, and incomplete test steps before implementation begins.
Essayez ces prompts
Create a First Plan
Create a draft implementation plan from [approved specification] and [interface document]. Check prerequisites and identify missing inputs before drafting tasks.
Define Testable Tasks
Refine [draft plan] into self-contained tasks. Include requirement IDs, exact interfaces, file lists, failing tests, expected results, and refactoring steps.
Split an Approved Specification
Use [decided decomposition session] to split [approved specification] into independently testable plans. Document coverage, predecessor assumptions, execution order, and dependency maps.
Audit and Repair the Plan Set
Audit [plan set] against [specification] and [interface contracts]. Repair coverage gaps, dependency cycles, and extraction defects. Report unavailable validation tools without claiming success.
Bonnes pratiques
- Confirm specification approval, interface contracts, and the human-selected decomposition before drafting tasks.
- Make each task independently understandable with exact requirements, interfaces, tests, and dependency references.
- Verify companion tools, use private temporary files, and inspect explicitly staged changes before the execution handoff.
Ăviter
- Inventing interfaces or architectural decisions inside an implementation plan.
- Using placeholders, implicit constraints, or references to another task instead of a complete acceptance contract.
- Starting implementation before regression clears and the human selects an execution mode.
Foire aux questions
Which AI tools are listed as supported?
The report lists Claude, Codex, and Claude Code. The workflow still requires the companion Executor resources and project documents.
What inputs are required before planning?
Provide an approved specification, relevant architecture decisions, and a decided decomposition session. Work spanning components also requires interface documents.
Does this package include the validation scripts?
No. This package contains only the planning instructions. The referenced scripts and supporting documents belong to the companion Executor package.
Can the skill invent missing interfaces?
No. Missing interfaces require an architecture decision before planning resumes. Task signatures must match the approved interface document.
When does implementation begin?
Implementation begins after plan regression clears and the human chooses subagent or inline execution. Planning does not authorize implementation by itself.
What security precautions apply to the examples?
Replace the shared temporary pathname with a private temporary directory. Stage only reviewed files and inspect staged changes before committing.