Feature sweep
Options: --skill , --feature , --since , --apply.
Workflow
- Identify the actual host, installed skill roots, version and exposed tools from
local context. Read names/descriptions first; filter by the requested scope.
- Check current official release notes and documentation for that host. Record the
date checked, release/version, source URL, availability and prerequisites for
each relevant feature. For OpenAI behavior check local version/configuration first
and use official OpenAI documentation as fallback. Use official GitHub/Microsoft
sources for Copilot. Treat unavailable browsing as an explicit research limitation.
- Map verified capabilities to concrete workflow steps: judgment, implementation,
context retrieval, review or repeated work. Read full instructions only for
candidates. Larger advertised context is not a reason to read unrelated files.
- Propose each change with skill/path, feature, before/after excerpt, expected benefit,
prerequisites, validation and risk. Distinguish released, preview and unavailable
features. Do not prescribe a model, tool or scheduler without verification.
- Default to a review report. --apply or a request to update skills authorizes the
scoped edits; apply relevant changes and validate metadata, references, scripts
and representative behavior. Preserve existing contracts and user configuration.
Stop only for material choices outside that authorization.
- Report applied, skipped and deferred opportunities with sources. Persist changes
through the owning repository's workflow. Create schedules only if explicitly
requested; an opportunity to automate is not authorization to register a job.
Example
"Check our review skills against the latest Copilot release" → date-stamped proposals
with official sources; no changes unless application was requested.
Closed decisions and open decisions
Preserve configured model, permissions and delivery choices. List uncertain capability
availability as open; do not silently turn a preview feature into a required dependency.
Do not
Do not use a hardcoded feature wish list as evidence, promise automatic runtime behavior
from prose alone, or apply speculative changes when sources cannot be checked.
Codex integration
Use $feature-sweep explicitly or let its description match the request. Resolve sibling
skills inside this plugin. Read AGENTS.md before repository edits; honor the current
host's tool access and delegation rules. Do not require another platform's runtime.
1---2name: feature-sweep-43description: Audit installed skills against verified current platform releases and propose or apply targeted improvements. Use after a Codex or Copilot release, or to find useful new integrations; use a skill quality audit for ordinary wording and trigger problems.4---56# Feature sweep78Options: --skill <name>, --feature <capability>, --since <date>, --apply.910## Workflow111. Identify the actual host, installed skill roots, version and exposed tools from12 local context. Read names/descriptions first; filter by the requested scope.132. Check current official release notes and documentation for that host. Record the14 date checked, release/version, source URL, availability and prerequisites for15 each relevant feature. For OpenAI behavior check local version/configuration first16 and use official OpenAI documentation as fallback. Use official GitHub/Microsoft17 sources for Copilot. Treat unavailable browsing as an explicit research limitation.183. Map verified capabilities to concrete workflow steps: judgment, implementation,19 context retrieval, review or repeated work. Read full instructions only for20 candidates. Larger advertised context is not a reason to read unrelated files.214. Propose each change with skill/path, feature, before/after excerpt, expected benefit,22 prerequisites, validation and risk. Distinguish released, preview and unavailable23 features. Do not prescribe a model, tool or scheduler without verification.245. Default to a review report. --apply or a request to update skills authorizes the25 scoped edits; apply relevant changes and validate metadata, references, scripts26 and representative behavior. Preserve existing contracts and user configuration.27 Stop only for material choices outside that authorization.286. Report applied, skipped and deferred opportunities with sources. Persist changes29 through the owning repository's workflow. Create schedules only if explicitly30 requested; an opportunity to automate is not authorization to register a job.3132## Example33"Check our review skills against the latest Copilot release" → date-stamped proposals34with official sources; no changes unless application was requested.3536## Closed decisions and open decisions37Preserve configured model, permissions and delivery choices. List uncertain capability38availability as open; do not silently turn a preview feature into a required dependency.3940## Do not41Do not use a hardcoded feature wish list as evidence, promise automatic runtime behavior42from prose alone, or apply speculative changes when sources cannot be checked.4344## Codex integration45Use `$feature-sweep` explicitly or let its description match the request. Resolve sibling46skills inside this plugin. Read AGENTS.md before repository edits; honor the current47host's tool access and delegation rules. Do not require another platform's runtime.
garyld1962