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.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
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.Your Agent should still show its plan and request any confirmation required by the security policy.
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "executor-spec". Draft acceptance requirements for placement requests that name an unknown cell.
Expected outcome:
Using "executor-spec". Assess placement latency risks before approving the specification.
Expected outcome:
Using "executor-spec". Change a requirement threshold after implementation plans already depend on the specification.
Expected outcome:
Most 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.
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
https://skillstore.io/skills/atri10-executor-spec/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/atri10-executor-spec?utm_source=security_passport_badge)<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><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>atri10. (2026). executor-spec security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/atri10-executor-spec/audits/1@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}
}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"
Convert approved design candidates into numbered requirements, constraints, scope exclusions, and linked acceptance criteria.
Connect failure scenarios to requirements, mitigations, accepted risks, and unresolved questions before authorizing planning.
Map requirements and constraints to named tests, manual steps, negative cases, boundary checks, and observable outputs.
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.
Author
atri10License
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
6d0b11444384184b7ae743742a7e233a9a705cd9
Maintenance freshness
10/6/2026
Usage
0 downloads · 0 views
File structure
Audit and Repair Plans Before Execution
Separate plans can hide missing requirements, incompatible interfaces, and broken dependencies. This skill reviews the complete plan set and coordinates repairs with independent verification.
Execute Approved Plans with Subagents and Reviews
Long implementation plans can lose task state and accumulate unreviewed changes. This skill coordinates scoped subagents, review gates, and durable records across execution and recovery.
Clarify Initiatives and Compare Approaches
Unclear requirements and unsupported assumptions make technical decisions difficult. This skill guides structured discovery, evidence gathering, and approach comparisons before human approval.
Verify Completion Claims With Recorded Evidence
Completion claims can hide failed, skipped, or untested requirements. This skill guides requirement-level verification with observed output, commit-bound evidence, and explicit human acceptance.
Prepare Executor Integration and Session Handoffs
Session changes can lose decisions, verification evidence, and unfinished implementation work. This skill guides human-controlled integration, durable pause records, and resumption checked against the current repository.
Audit and Repair Initiative Artifacts
Conflicting documents can carry incorrect decisions into later development phases. This skill coordinates independent audits, scoped repairs, and fresh re-audits before phase clearance.
Plan Software Projects With Structured Documents
by Dwsy
Software projects often fail when requirements, design choices, and tasks are unclear. This skill turns project ideas into structured planning documents for Claude, Codex, and Claude Code workflows.
Build Federal SOW and PWS Documents
by 1102tools-dev
Federal acquisition teams need measurable requirements without mixing pricing content into the contract document. This skill builds structured SOW or PWS files and separate internal handoffs.
Create Confirmation-Driven PRDs
by yunshu0909
PRD work often becomes vague, unconfirmed, or hard to hand off. This skill guides structured discovery, story confirmation, diagrams, and final PRD generation.
Manage Requirement Changes Safely
by yunshu0909
Requirement changes often expand across files without clear approval points. This skill gives Claude, Codex, and Claude Code a gated workflow for scope, impact, validation, and documentation.
Structure AI Development With Specs
by 89jobrien
Complex AI-assisted projects can lose clarity before implementation starts. This skill guides teams through phased specifications, governance, planning, analysis, and task execution.
Enforce Waterfall Phase Gates
by Chemiseblanc
AI coding sessions can skip requirements, design, or testing when pressure rises. This skill keeps work inside a strict waterfall flow with documented gates.