ctf-writeup

Generate a standardized submission-style CTF writeup for a solved challenge. Default behavior: Collect the following from the current session, challenge files, and user input: Write the writeup file as writeup.md (or writeup- .md ) using the submission template below. Guidance: Before finalizing the writeup, verify: DO: DON'T: $ARGUMENTS - During an active competition, optimize for speed, clarity, and reproducibility - Keep writeups short enough that a teammate or organizer can validate the solve quickly - Always produce a submission -style writeup - Prefer one complete solve script from challenge data to final flag - Challenge metadata — name, CTF event, category, difficulty, points, flag format - Solution artifacts — exploit scripts, payloads, screenshots, command output - Timeline — key steps taken, dead ends, pivots - Prefer 1-3 short steps total - Keep code to the smallest complete solving script - Do not split "recover secret", "derive key", and "decrypt flag" into separate partial snippets - The script should start from the challenge data and end by printing the flag - Avoid long background sections - Avoid dead ends unless they explain a key pivot - Avoid multiple alternative solves; pick one clean path - Redact the flag only if the user explicitly asks for redaction - Explain just enough for fast verification - Include one complete solving path, not multiple...