issues-report

スター12

フォーク5

更新日2026年7月27日 14:34

Produce a read-only maintainer briefing from ThreatForge Project 2

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

ソース

exit-zero-labs

exit-zero-labs/threat-forge

ダウンロード

Issues report

Produce a read-only, reproducible briefing. Do not mutate GitHub or repository files.

Record the current main commit, open PR set, and report timestamp.
Query Project 2 fields and open issue bodies.
Separate:
- AUTO executable work
- partly blocked work with the concrete blocker
- owner-only/HITL decisions
- unresolved Backlog intake
Map parent/sub-issue and dependency relationships.
Lead with one recommended maintainer action and why.
Use asymmetric depth: more detail for high-impact or ambiguous items, less for settled work.
Save any long artifact outside the repository or in a gitignored session artifact directory.

Never infer readiness from labels alone; confirm criteria, dependencies, Effort, and plan state.

このリポジトリの他の Skills

同じリポジトリ

Select the next executable AUTO ThreatForge issue

Shape one ThreatForge issue and populate Project 2 metadata without coding

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

Coordinate an explicitly authorized ThreatForge PR lifecycle through owner validation

name	issues-report
description	Produce a read-only maintainer briefing from ThreatForge Project 2

Produce a read-only, reproducible briefing. Do not mutate GitHub or repository files.

Record the current main commit, open PR set, and report timestamp.
Query Project 2 fields and open issue bodies.
Separate:
- AUTO executable work
- partly blocked work with the concrete blocker
- owner-only/HITL decisions
- unresolved Backlog intake
Map parent/sub-issue and dependency relationships.
Lead with one recommended maintainer action and why.
Use asymmetric depth: more detail for high-impact or ambiguous items, less for settled work.
Save any long artifact outside the repository or in a gitignored session artifact directory.

Never infer readiness from labels alone; confirm criteria, dependencies, Effort, and plan state.