Publish planner and implementer role guidance v0.2.0
Check instruction packages / check (push) Successful in 3s
Check instruction packages / check (pull_request) Successful in 3s

This commit is contained in:
admin committed 2026-10-05 15:20:12 -04:00
1 parent 370416b87b
commit 370ebd572f
9 files changed
+95 -10

No files matched your search

+15
View File
@@ -0,0 +1,15 @@
---
name: implementer-handoff
description: Reconcile verified implementation documentation and prepare review content during implementation.
metadata:
relayview-display-name: Implementer handoff
relayview-version: 0.2.0
---
# Implementer handoff
During the assigned implementation step, keep the repository's current-behavior documentation aligned with the code and checks you actually completed. Read the project's documentation rules and the relevant existing contract before editing it. Use the [handoff guide](handoff.md) for the documentation disposition and review content.
Prepare a concise, attributable review handoff when the assigned workflow gives you a place to submit one. Identify the exact candidate, focused checks and their observed results, any manual evidence and its observer, unresolved limitations, and the documentation disposition. A command attempted is not a check passed; report failures and stale evidence explicitly.
Use only the Implementer's assigned tools and owner interfaces. The owner verifies validation, review, provider effects, and stage readiness; your prose is a report for that process. This step is complete when documentation describes verified behavior and the handoff lets a reviewer reproduce the relevant checks.
+14
View File
@@ -0,0 +1,14 @@
# Handoff guide
## Documentation
- Update the current-behavior contract only for behavior verified on the candidate. Keep proposed work clearly proposed.
- Record one disposition: `updated`, `not_required` with a concrete reason, `deferred`, or `blocked`.
- Put run-specific logs, screenshots, and command results in the review handoff, not the enduring contract, unless the contract explicitly depends on one identified run.
## Review content
- Summarize the user-visible change and its bounded impact.
- Name the candidate revision and the focused checks run against it, with observed pass or failure results.
- Give a reviewer executable steps and expected observations for any behavior that automated checks cannot establish.
- State remaining uncertainty and recovery steps. Attribute provider or Human observations to their actual source.
@@ -0,0 +1,19 @@
{
"schemaVersion": 1,
"source": {
"kind": "first-party",
"reference": "v0.2.0"
},
"role": "implementer",
"step": "implementation",
"files": [
{
"path": "SKILL.md",
"sha256": "bfeafa2d7780fe2c0bb4206ab9a03acd12804347ceb0f3ffb3e06e1be514c852"
},
{
"path": "handoff.md",
"sha256": "303c3e792cf0e8da6215e6eeb69f5a2f1f2bd0b67db016160d9e83a970ad95d3"
}
]
}