task-executor
/task-executor
Use this skill to implement one exact SPIDER task. The executor follows the planner-owned observable contract, makes only reversible file-local choices, records task-scoped changes, and moves completed implementation to Ready for validation. It never marks a task Done.
- Author
- Algoza-Solutions ↗
- Repository
- spider-protocol ↗
- Licence
- MIT
- Last repository change
- 02.11.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 02.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use this skill to implement one exact SPIDER task. The executor follows the planner-owned observable contract, makes only reversible file-local choices, records task-scoped changes, and moves completed implementation to Ready for validation. It never marks a task Done.
Original author description
Use this skill to implement one exact SPIDER task. The executor follows the planner-owned observable contract, makes only reversible file-local choices, records task-scoped changes, and moves completed implementation to Ready for validation. It never marks a task Done.
How it works
- Load the operating contract
- Keep immutable records newest-first
- Record ISO 8601 timestamps
SKILL.md preview
--- name: task-executor description: "Use this skill to implement one exact SPIDER task. The executor follows the planner-owned observable contract, makes only reversible file-local choices, records task-scoped changes, and moves completed implementation to Ready for validation. It never marks a task Done." --- # Task Executor Adopt this specialist role for the current request. ## Load the operating contract Read [role-instructions.md](references/role-instructions.md) completely before taking any task action. Apply it as the role's mandatory operating contract. - Interpret references to `this agent` as the coding agent instance using this skill. - Treat source-role boundaries, artifact ownership, state transitions, and exact output contracts as binding. - Follow system, developer, and explicit user instructions when they override the role contract. - Use only the portions of the contract relevant to the current invocation, while honoring every prerequisite and guard it names. ## Keep immutable records newest-first Treat "append" as an immutable addition, not as end-of-file placement. When adding an entry to any append-only SPIDER document, ledger, table, or log, insert the complete new entry before older entries, immediately after the fixed document title and preamble, table header, or owning section heading. This includes `requirements.md`, `decisions.md`, task `## LOG` and `## DEBUG LOG` sections, and equivalent histories. Never reorder, rewrite, or delete existing entries unless an explicit cleanup contract authorizes it. ## Record ISO 8601 timestamps Every new SPIDER progress/history record that this skill creates or updates uses the actual current time as a second-precision ISO 8601 timestamp with timezone offset (`YYYY-MM-DDTHH:mm:ss?HH:mm` or `Z`). Do not emit date-only output. Preserve historical date-only evidence without inventing times.
Files in this package (3)
- SKILL.md 2 KB
- agents/openai.yaml 1 KB
- references/role-instructions.md 18 KB
Versions
The database has no other skills named task-executor.
Database snapshot: 13.11.2026 · package version 0e5af352fa0a (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100spider-orchestrator
Coordinate software delivery in repositories that use the SPIDER protocol. Use when the coding agent must act as the SPIDER orchestrator: investigate and clarify a new change request conversationally before documentation or routing, write a free-form detailed requirements file… - 100planner
Use this skill when structured planning is required in a SPIDER protocol project. The planner is the peer Tech Lead: it owns minimum-sufficient implementation design under KISS, creates the fewest cohesive tasks within architect-owned boundaries, and writes typed, resumable… - 82implement-work
Use to implement one PR-sized task. - 100ywc-sequential-executor
(ywc) Use when executing tasks from the tasks/ directory in strict order through their full lifecycle. Triggers: "execute task", "implement tasks 000001-010", "run the next task", "implement all remaining tasks", "start implementing", "sequential-executor", "순차 실행", "タスク順次実行".… - 100ywc-sequential-executor
(ywc) Use when executing tasks from the tasks/ directory in strict order through their full lifecycle (branch → implement → commit → PR → CI → merge → cleanup). Triggers: "execute task", "implement tasks 000001-010", "run the next task", "implement all remaining tasks", "start… - 90info-spider
WeChat Official Account article crawler (微信公众号爬虫) CLI tool built in Rust. Use this skill when working on the info-spider crate, debugging spider commands, adding features, or when the user mentions 微信, WeChat, 公众号, official account, article scraping, MP platform, or info-spider.…