Loading…
Scope a loose engineering task into a tight, testable spec list. Use when the user gives background for a piece of work and wants the requirements narrowed down before implementation. Trigger phrases include: "scope this", "what are the specs", "what's involved", "what would it take", "what's left for this task", "port this to", "bring this logic to", and "spec this ticket/issue". This skill defines WHAT must be true when the work is done — it does not produce an implementation plan, task ordering, or execution steps. For sequencing the specs into ordered, verifiable tasks, use planning-and-task-decomposition instead.
task-scope-and-spec is an agent skill entry in ChatHome Skills, sourced from GitHub Skill Search and scored 58/100. # task-scope-and-spec ## Purpose Turn loose task context — a description, ticket, link, branch, diff, or existing code — into a small, accurate spec list. Gathe. As an agent skill, it packages a reusable instruction set that AI coding agents such as Codex and Claude Code can load to perform this task without hand-written glue code. ChatHome Skills discovered this entry through its daily ingest of official registries and GitHub discovery queries, and re-verifies repository facts, freshness signals, and install metadata on every run. The quality score weighs official-registry presence, a working install command, license clarity, GitHub star trajectory, and repository freshness — the full formula is on the Sources page. The install command above is ready to copy. Review the last-pushed date and repository status before adding task-scope-and-spec to a production agent workflow; the snapshot facts below are point-in-time values from the most recent ingest.
codex skill install pytholic/claude-skillsReview the upstream source before running this command.
Scan coverage: Install metadata and the indexed document body.
Automated signals from install metadata and a bounded skill body — not a full code security audit and not a recursive source or dependency review.
# task-scope-and-spec ## Purpose Turn loose task context — a description, ticket, link, branch, diff, or existing code — into a small, accurate spec list. Gather the relevant conte