context-packet-fastpath
/context-packet-fastpath
Use to prepare a minimal context packet for a delegated subtask or to consume a frozen packet without re-reading unrelated files.
- Author
- funky-eyes ↗
- Repository
- best-copilot ↗
- Licence
- Apache-2.0
- Last repository change
- 04.08.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 04.08.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Use to prepare a minimal context packet for a delegated subtask or to consume a frozen packet without re-reading unrelated files.
Original author description
Use to prepare a minimal context packet for a delegated subtask or to consume a frozen packet without re-reading unrelated files.
How it works
- Packet Fields (by block)
- Artifact Reuse Contract
- Token Cost Metrics
- Rules
SKILL.md preview
--- name: context-packet-fastpath description: "Use to prepare a minimal context packet for a delegated subtask or to consume a frozen packet without re-reading unrelated files." --- # Context Packet Fastpath Uses the six-block PM dispatch packet from `core-workflow-contract`. This skill lists all fields grouped by block for quick reference. ## Packet Fields (by block) ### 1. task_intent `goal`, `user_provided_paths`, `user_intent_summary`, `expected_outcome`, `task_type` (`implementation | design_review | verification | fix | spec`), `work_mode` (`micro | standard | full`) ### 2. frozen_scope `scope`, `non_goals`, `files_involved`, `changed_files`, `priority_files`, `already_read_files`, `dependencies`, `owner_lane`, `reviewer_lanes`, `write_set`, `parallel_group`, `review_package_ref`, `diff_ref`, `task_brief_ref`, `acceptance_ref`, `context_shards` ### 3. fact_packet `authoritative_repo_facts`, `source_provenance_refs`, `reference_files` ### 4. execution_contract `assumptions`, `tradeoffs`, `simpler_option_considered`, `constraints`, `acceptance_checks`, `verification_budget`, `search_hints`, `context_budget` (max files/shards before returning for scope widening), `model_policy`, `model_cost_boundary`, `cost_boundary`, `reviewer_input_boundary`, `reviewer_permission_boundary`, `final_independent_review`, `stop_conditions`, `forbidden_approaches`, `read_before_write_targets` ### 5. review_state `review_followup_scope`, `previously_verified_items`, `review_lanes`, `ready_artifacts` (files, commands, screenshots, review outputs already produced) ### 6. output_contract `required_artifacts`, `recommended_next_stage`, `dispatch_reason`, `retrieval_provenance`, `memory_refs`, `spec_refs` ## Artifact Reuse Contract Use `artifact_refs` when evidence is shared across lanes instead of copying the content into each prompt: ```text artifact_ref: kind: diff | context | verification | review | search_result | state_update | metric | evolution path_or_command: producer: scope: freshness_or_base_head: summary: recovery_note: sensitive_data_checked: yes | no | n/a ``` Delegates read artifact refs first and reopen search only when refs are stale, incomplete, contradicted, or outside `context_budget`. ## Token Cost Metrics Track lightweight metrics when practical: `files_read`, `broad_searches`, `context_budget_used`, `artifact_reuse_count`, and `escalation_reason`. These are optimization signals only; do not hide raw failure evidence, verification output, or residual risk to make numbers look better. ## Rules - Lean packet: enough for one small task. - Full packet: needed only for cross-module or high-risk work. - Prefer `micro` or `standard` packets when the file set and acceptance checks are already clear. - Prefer file-backed refs (`review_package_ref`, `diff_ref`, `task_brief_ref`, `acceptance_ref`, `context_shards`) over pasting large diffs, logs, specs, screenshots, or repeated context into multiple agents. - Do not include whole logs, whole specs, or unrelated memory. - Include recovery pointers for omitted detail so a delegate can fetch only the needed shard. - Include only the retrieval provenance needed to justify selected files. - Include material assumptions and tradeoffs only when they affect implementation, routing, or verification; do not pad the packet with obvious facts. - For code-editing packets, include read-before-write targets: the file public surface/exports, immediate caller/callee, and obvious shared utility/local pattern to inspect. - For review packets, include allowed evidence and forbidden influence: no controller severity opinion, author merge recommendation, approval framing, or unverifiable status claim. - If a delegate needs new files, return to PM to widen scope. - A delegate must consume `task_type`, `user_intent_summary`, `review_followup_scope`, `previously_verified_items`, `ready_artifacts`, file-backed refs, `required_artifacts`, and `recommended_next_stage` before reopening search. - A delegate should stop at `context_budget` and return `NEEDS_CONTEXT` instead of broad-scanning. - A delegate should treat `authoritative_repo_facts` and `source_provenance_refs` as fixed context unless the packet says they are provisional. - Follow the Specialist Ask Boundary from `core-workflow-contract`.
Versions
The database has no other skills named context-packet-fastpath.
Database snapshot: 13.11.2026 · package version 5f4589da53fd (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
- 100search-fastpath
Use when target files are unknown, repeated search is becoming expensive, an agent is about to do broad repo-wide scanning, or a regex search is being considered. DO NOT USE FOR: explicit user paths or already frozen files_involved. - 90prompt-reference-packet
Use when the task is to prepare a compact, role-labeled reference packet for a generation agent. - 100packet-worker
Use when you are dispatched as a worker on one packet of a larger task — execute only your packet, stay inside your file ownership, verify it, and report a clear status. Load this before touching code in a packet. - 90spec-execution-fastpath
Use when requirements or spec are clear and the implementation should be a minimal, repo-pattern-compatible diff. DO NOT USE FOR: unclear direction, broad redesign, or tasks without enough file/context evidence. - 100skill-router
Route tasks to local skills. Use when choosing skills, recovering omitted skills after context warnings, or preparing a small skill context packet. NOT for install, authoring, or audit workflows. - 100context-pack
Creates structured handoff briefings between agents. Use when delegating complex work to subagents that would otherwise lose context. Packages task context, constraints, and progress into a compact packet that subagents can consume without re-reading the full conversation.…