Menu
Standard progress report format, location conventions, and handoff documentation for all agents
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/tardyp/esp_tock --skill progress-reportingThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
ESP32-C6 hardware specifics - register addresses, peripherals, and RISC-V considerations
Hardware test automation patterns for ESP32-C6, similar to Tock's existing test infrastructure
Global issue tracker management - creating issues, severity levels, and tech debt tracking
Based on SOC occupation classification
| name | progress_reporting |
| description | Standard progress report format, location conventions, and handoff documentation for all agents |
| license | MIT |
| compatibility | opencode |
| metadata | {"category":"methodology","for_agent":"all","focus":"communication, traceability"} |
All reports go in the sprint folder with Supervisor-assigned numbers:
project_management/PI###_Name/SP###_Name/{number}_{agent}_{topic}.md
Example:
project_management/PI001_First_Boot/SP001_Setup/
001_analyst_research.md
002_implementor_tdd.md
003_integrator_hardware.md
004_reviewer_report.md
005_supervisor_summary.md
Only Supervisor assigns numbers. Request your number in the delegation.
# PI###/SP### - [Agent] Report: [Topic]
## Session Summary
**Task:** [Brief description]
**Status:** [Complete / In Progress / Blocked]
## Work Completed
- [x] Item 1
- [x] Item 2
- [ ] Item 3 (incomplete - reason)
## Key Findings / Decisions
[Important discoveries or choices made]
## Issues Encountered
| Issue | Resolution | Impact |
|-------|------------|--------|
| [Problem] | [How solved or escalated] | [Effect on timeline] |
## Handoff Notes
[Critical information for next agent]
## Next Steps
[What should happen next]
## Research Summary
[Findings from investigation]
## Questions for PO
[Via USER_QUESTIONS.md]
## Risks Identified
| Risk | Likelihood | Mitigation |
## TDD Metrics
- Cycles: X / target <15
- Tests written: N
- Tests passing: N
## Quality Status
- clippy: PASS/FAIL
- fmt: PASS/FAIL
## Hardware Test Results
| Test | Status | Notes |
|------|--------|-------|
## Debug Artifacts
[Logs, captures, observations]
## Escalations
| Issue | Reason | To |
## Verdict
[APPROVED / REQUIRES_CHANGES / APPROVED_WITH_TECHDEBT]
## Issues Created
| ID | Severity | Title |
Write report at END of every session before returning control.
Mandatory - No exceptions.
Good handoff notes include:
Bad handoff notes:
Reference issue_tracker.yaml IDs when relevant:
## Related Issues
- Issue #5: GPIO interrupt not firing (created this sprint)
- Issue #2: Timer accuracy concern (existing techdebt)