issues-clarify

النجوم١٢

التفرعات٥

آخر تحديث٢٧ يوليو ٢٠٢٦ في ١٤:٣٤

Re-derive and repair the ThreatForge GitHub board after roadmap or code drift

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

المصدر

exit-zero-labs

exit-zero-labs/threat-forge

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

SKILL.md

readonly

name	issues-clarify
description	Re-derive and repair the ThreatForge GitHub board after roadmap or code drift

Issues clarify

Run as an explicit maintainer-requested board maintenance pass.

Record the current main commit and all open PRs for a reproducible snapshot.
Discover Project 2 fields/options dynamically.
Review every non-Done issue against current code, merged work, open PRs, parent initiatives, dependencies, and roadmap direction.
Identify obsolete, duplicate, compound, blocked, or wrongly prioritized work, and work whose Effort no longer matches the reasoning it actually needs. Raise an understated Effort before acting on the issue: cryptography, the IPC boundary, the .thf schema, and trust boundaries are High however small the diff looks.
Preserve Backlog for genuinely unshaped reports.
Split compound executable work into native sub-issues; a High issue stays the parent of the sub-issues it decomposes into.
Ensure exactly one autonomy label and explicit acceptance/dependency state.
Mutate one item at a time, read it back, and leave a concise reason for material changes.
Report the snapshot, changes, unresolved decisions, and remaining drift.

Do not alter repository code or invent product decisions.

المزيد من هذا المستودع

نفس المستودع

autonomous-issue-triage

exit-zero-labs/threat-forge

Select the next executable AUTO ThreatForge issue

2026-07-2712

issue-triage

exit-zero-labs/threat-forge

Shape one ThreatForge issue and populate Project 2 metadata without coding

2026-07-2712

fix-issue

exit-zero-labs/threat-forge

Compatibility alias for implementing a settled ThreatForge bug issue

2026-07-2712

implement-issue

exit-zero-labs/threat-forge

Orchestrate one settled ThreatForge issue through verification and preflight

2026-07-2712

issues-report

exit-zero-labs/threat-forge

Produce a read-only maintainer briefing from ThreatForge Project 2

2026-07-2712

pr-cycle

exit-zero-labs/threat-forge

Coordinate an explicitly authorized ThreatForge PR lifecycle through owner validation

2026-07-2712

name	issues-clarify
description	Re-derive and repair the ThreatForge GitHub board after roadmap or code drift

Issues clarify

Run as an explicit maintainer-requested board maintenance pass.

Record the current main commit and all open PRs for a reproducible snapshot.
Discover Project 2 fields/options dynamically.
Review every non-Done issue against current code, merged work, open PRs, parent initiatives, dependencies, and roadmap direction.
Identify obsolete, duplicate, compound, blocked, or wrongly prioritized work, and work whose Effort no longer matches the reasoning it actually needs. Raise an understated Effort before acting on the issue: cryptography, the IPC boundary, the .thf schema, and trust boundaries are High however small the diff looks.
Preserve Backlog for genuinely unshaped reports.
Split compound executable work into native sub-issues; a High issue stays the parent of the sub-issues it decomposes into.
Ensure exactly one autonomy label and explicit acceptance/dependency state.
Mutate one item at a time, read it back, and leave a concise reason for material changes.
Report the snapshot, changes, unresolved decisions, and remaining drift.

Do not alter repository code or invent product decisions.