القائمة
Global issue tracker management - creating issues, severity levels, and tech debt tracking
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/tardyp/esp_tock --skill issue-trackingيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Standard progress report format, location conventions, and handoff documentation for all agents
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
عرض SKILL.md
استنادا إلى تصنيف SOC المهني
| name | issue_tracking |
| description | Global issue tracker management - creating issues, severity levels, and tech debt tracking |
| license | MIT |
| compatibility | opencode |
| metadata | {"category":"methodology","for_agent":"reviewer, supervisor","focus":"quality, traceability"} |
project_management/issue_tracker.yaml
# Global Issue Tracker for Tock ESP32-C6 Port
next_id: 5 # Always increment after creating issue
issues:
- id: 1
severity: critical
type: bug
title: "Short description"
status: open
sprint: PI001/SP001
created_by: reviewer
created_at: 2024-01-15
resolved_at: null
notes: "Additional context"
issue_tracker.yamlnext_id valuenext_id# Before
next_id: 5
issues:
- id: 4
...
# After adding new issue
next_id: 6
issues:
- id: 4
...
- id: 5
severity: medium
type: bug
title: "GPIO interrupt not triggering"
status: open
sprint: PI001/SP002
created_by: reviewer
created_at: 2024-01-20
resolved_at: null
notes: "Works in test, fails on hardware"
| Severity | Description | Sprint Impact |
|---|---|---|
| critical | Blocks functionality, safety issue | Must fix before approval |
| high | Significant bug, wrong behavior | Must fix before approval |
| medium | Code quality, minor bug | Should fix, can defer |
| low | Style, docs, nice-to-have | Defer to TechDebt PI |
| Type | Description |
|---|---|
| bug | Something doesn't work correctly |
| techdebt | Known shortcut or cleanup needed |
| enhancement | Improvement opportunity |
| question | Needs PO/Analyst input |
| Status | Meaning |
|---|---|
| open | Issue identified, not started |
| in_progress | Currently being worked on |
| resolved | Fixed and verified |
| wont_fix | Decided not to fix (document reason) |
CRITICAL: IDs are NEVER reused
next_id and increment after useFor issues that cannot be fixed immediately:
- id: 7
severity: medium
type: techdebt
title: "Timer accuracy could be improved"
status: open
sprint: PI001/SP003
created_by: reviewer
created_at: 2024-01-25
resolved_at: null
notes: |
Current accuracy is 15%, acceptable for MVP.
Should target 5% in TechDebt PI.
See PI001/SP003/004_reviewer_report.md for details.
When fixing an issue:
- id: 5
severity: medium
type: bug
title: "GPIO interrupt not triggering"
status: resolved # Changed from open
sprint: PI001/SP002
created_by: reviewer
created_at: 2024-01-20
resolved_at: 2024-01-22 # Add resolution date
notes: |
Works in test, fails on hardware.
RESOLVED: Fixed in PI001/SP003 - interrupt enable bit was wrong.
Commit: abc123
In commit messages:
feat(gpio): implement interrupt handling
Fixes #5: GPIO interrupt not triggering
Related: #3 (timer accuracy)
In reports:
## Issues
- Fixed Issue #5: GPIO interrupt
- Created Issue #8: Timer drift concern
Periodically, schedule a TechDebt PI:
issue_tracker.yaml for type: techdebt and status: openresolvedSupervisor ensures PO is aware of: