issue-triage
Shape one ThreatForge issue and populate Project 2 metadata without coding
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Shape one ThreatForge issue and populate Project 2 metadata without coding
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Select the next executable AUTO ThreatForge issue
Compatibility alias for implementing a settled ThreatForge bug issue
Orchestrate one settled ThreatForge issue through verification and preflight
Re-derive and repair the ThreatForge GitHub board after roadmap or code drift
Produce a read-only maintainer briefing from ThreatForge Project 2
Coordinate an explicitly authorized ThreatForge PR lifecycle through owner validation
| name | issue-triage |
| description | Shape one ThreatForge issue and populate Project 2 metadata without coding |
| argument-hint | [issue-number] |
Triage one issue. Do not plan Medium or High work, and do not edit production code.
AGENTS.md, the full issue/comments, related issues/PRs, roadmap context, and relevant
repository evidence.SECURITY.md.Status is a project field, so gh project field-list
finds it. Priority, Effort, and Type are native org issue fields and do not appear
there at all — enumerate them from organization.issueFields and organization.issueTypes
on the GraphQL API, and write them with setIssueFieldValue / updateIssueIssueType. Reading
them through the project API returns nothing and raises no error, which reads as "unset" on a
board that is fully populated.Task, Bug, or FeaturePriority: High/Medium/Low, answering how soon within the milestone.
High requires a comment naming what specifically goes wrong if this waits. The field's
Urgent option is never assigned; High is the ceiling.Effort: the reasoning class the work needs, not how long it takes — High/Medium/Low
with the matching model/opus|sonnet|haiku label. It is a floor: cryptography, the IPC
boundary, the .thf schema, and trust boundaries are High however small the diff looks.AUTO or HITLReady only when executable; otherwise Backlog## Triage rationale in the issue or a maintainer comment.Never treat reporter urgency as maintainer priority without triage evidence.