executor-spec
Write Testable Specifications Before Planning
Ambiguous requirements create conflicting implementations and unverifiable reviews. This skill guides linked specifications, risk assessments, and verification strategies through explicit human approval.
Installer avec mon Agent
Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.
Review the Skillstore skill "executor-spec" from https://skillstore.io/skills/atri10-executor-spec.md and its manifest at https://skillstore.io/api/skills/atri10-executor-spec/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-spec ». Draft acceptance requirements for placement requests that name an unknown cell.
RĂ©sultat attendu:
- Requirement R02: A request naming an unavailable cell returns HTTP 422 with the error value unknown_cell.
- Observable: The response contains the required status and error value; no placement row is added.
- Verification: One criterion checks the rejection response, and another checks the absence of a stored placement.
- Review state: Draft awaiting explicit human approval.
Utilisation de « executor-spec ». Assess placement latency risks before approving the specification.
RĂ©sultat attendu:
- Failure scenario: Placement latency exceeded the agreed threshold as tenant count increased.
- Cause: The available-cell scan was not measured at the expected tenant scale.
- Mitigation: Add a measurable latency requirement and a linked load-test criterion.
- Evidence plan: Record the observed percentile latency at the specified tenant count; keep the criterion pending until execution.
Utilisation de « executor-spec ». Change a requirement threshold after implementation plans already depend on the specification.
RĂ©sultat attendu:
- Change classification: Material because the new threshold can change implementation and review outcomes.
- Document action: Create a replacement specification and preserve the previous specification body.
- Traceability: Keep surviving requirement numbers and relink the verification strategy to the replacement.
- Plan impact: Record which dependent plans need revision and which remain unaffected.
Audit de sécurité
SûrMost findings are Markdown formatting, legitimate test examples, or fixed sibling references, not shell substitution, reconnaissance, or exploitable traversal. The verification example writes to predictable /tmp/b, creating a local symlink overwrite risk if copied and executed. No evidence found of credential exfiltration or prompt injection; referenced sibling helpers are outside the reviewed package.
ĂlĂ©ments dâĂ©valuation des capacitĂ©s (1)
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Ă©.
Facteurs de risque
âïž Commandes externes (50)
đ AccĂšs rĂ©seau (1)
đ AccĂšs au systĂšme de fichiers (16)
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-spec/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportBadge Markdown
[](https://skillstore.io/skills/atri10-executor-spec?utm_source=security_passport_badge)Badge HTML
<a href="https://skillstore.io/skills/atri10-executor-spec?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/atri10-executor-spec/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Carte intégrable
<iframe src="https://skillstore.io/embed/skills/atri10-executor-spec.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-spec security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/atri10-executor-spec/audits/1Citation BibTeX
@techreport{atri10-atri10-executor-spec-2026,
author = {atri10},
title = {executor-spec security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/atri10-executor-spec/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-spec 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-spec/audits/1"
identifiers:
- type: other
value: "skillstore:atri10-executor-spec:audit:1"
description: "Skillstore immutable audit report identifier"
Score Skillstore
Pourquoi ce score Niveau de confiance des preuves: MoyenCe que vous pouvez créer
Prepare an implementation specification
Convert approved design candidates into numbered requirements, constraints, scope exclusions, and linked acceptance criteria.
Review delivery risks before approval
Connect failure scenarios to requirements, mitigations, accepted risks, and unresolved questions before authorizing planning.
Define auditable acceptance evidence
Map requirements and constraints to named tests, manual steps, negative cases, boundary checks, and observable outputs.
Essayez ces prompts
Use executor-spec to draft requirements from [approved design handoff] for [initiative]. Include constraints, exclusions, and owned questions. Stop for human review before planning.
Review [draft specification] with executor-spec. Write a failure narrative, trace causes, assign mitigation links, and document accepted risks. Update affected requirements before approval.
Create a verification strategy for [specification]. Cover every requirement and constraint with exact procedures and expected observations. Include rejection and boundary checks. Keep results pending.
Assess [proposed change] against [specification] and [dependent plans]. For material changes, preserve existing IDs, draft supersession documents, relink verification, and record plan impacts.
Bonnes pratiques
- Provide the approved design handoff, charter, architecture records, and interface documents before drafting requirements.
- Use exact thresholds and observable outcomes, then map every requirement and constraint to verification evidence.
- Review companion helpers before execution, use private temporary files, and require explicit approval before passing the phase gate.
Ăviter
- Replace missing decisions with vague terms such as appropriate, robust, or performant.
- Claim tests passed when the document only defines expected evidence.
- Edit material requirements in place after dependent plans exist, or treat silence as approval.
Foire aux questions
Which AI tools can use this skill?
What documents does this workflow produce?
Does the package include the Executor helper scripts?
Does creating verification criteria mean the tests passed?
Can an approved specification be changed?
Are there precautions before running example commands?
Détails du développeur
Auteur
atri10Licence
MIT
RĂ©vision Skillstore
r1
Avis de version
Lâauteur nâa dĂ©clarĂ© aucune version.
RĂ©f
6d0b11444384184b7ae743742a7e233a9a705cd9
RĂ©cence de maintenance
06/10/2026
Utilisation
0 téléchargements · 0 vues
Structure de fichiers