Skip to content

Feature/require purple team before report - #7

Merged
BuildAndDestroy merged 3 commits into
mainfrom
feature/require-purple-team-before-report
Sep 13, 2026
Merged

BuildAndDestroy merged 3 commits into
mainfrom
feature/require-purple-team-before-report

Conversation

@BuildAndDestroy

Copy link
Copy Markdown
Owner

No description provided.

BuildAndDestroy and others added 3 commits September 12, 2026 23:14
A close-out jump to the report was skipping Skill 4; the session prompt and skills now refuse to start reporting until atomics/ YAML and markdown exist for every positive finding.

Co-authored-by: Cursor <cursoragent@cursor.com>
… in-repo.

Operators already have the template in Ghostwriter. The reporting skill still follows that flow via ghostwriter-executive-template.md.

Co-authored-by: Cursor <cursoragent@cursor.com>
PR #6 landed the JSON context object; this keeps that schema while still refusing to report without atomics/ files and without shipping the executive .docx.

Co-authored-by: Cursor <cursoragent@cursor.com>
@BuildAndDestroy
BuildAndDestroy merged commit 93ff251 into main Sep 13, 2026
5 checks passed
@BuildAndDestroy
BuildAndDestroy deleted the feature/require-purple-team-before-report branch September 13, 2026 05:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant