Doc status report create
Skill JasonWarrenUK/goblin-mode/skills/doc-status_report-create
Three goblins in a trenchcoat pretending to be a senior developer. Claude Code config shaped by ADHD, friction, and spite.
npx -y skills add JasonWarrenUK/goblin-mode --skill doc-status_report-createAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
{{ 𝚫𝚫𝚫 }} Create a status report that knows what you've done since the last one
SKILL.md
2.9 KB, as published. Nobody here has run it
<task overview="Generate a project status report by analysing the current state of the codebase, roadmaps, and recent work." destination="docs/dev-log/status-reports/" >
<filename format="{PROJECT-REPORT-NUMBER}_{YY-MM-DD-HHMM}_{RECENT}.md" example="003_26-01-13-1545_xml-validation-added.md" >
| Component | Description | Example |
|---|---|---|
| PROJECT-REPORT-NUMBER | 3-digit incrementing number across all reports | 001, 002, 015 |
| YY-MM-DD-HHMM | Date and time (24hr) | 26-01-13-1430 |
| RECENT | Most significant change, max 3 words, kebab-case | csv-parser-complete |
To determine PROJECT-REPORT-NUMBER, check existing reports in the output directory. </filename> <instructions>
- Read the roadmap —
python3 "$HOME"/.claude/library/scripts/roadmap.py statswhen a rich roadmap exists (check withroadmap.py detect), otherwise the newest file indocs/roadmaps/ - Check recent work records in
docs/dev-log/work-records/for recent activity - Review git history in one command:
"$HOME"/.claude/library/scripts/git-doc-history.sh {previous-report-path} .— commits, file changes and diff stat since the last report; accurate numbers, not estimates - Identify blockers from any TODO comments, failing tests, or documented issues
- Read the previous status report in
docs/dev-log/status-reports/to understand what was last reported as completed, in progress, and upcoming
- Audience: One dev, one non-dev - explain capabilities, not implementation
- Section 1 (What Happened): 2-3 sentences, big picture narrative
- Section 2 (Shipped): 3-5 concrete deliverables described by what they do
- Section 3 (Currently Working On): Honest about current state, no percentages
- Section 4 (Up Next): 2-4 items, acknowledge uncertainty
- Section 5 (Worth Remembering): Include meaningful context - decisions, dead ends, learnings
- Group related work (e.g. "CSV parser with validation and tests")
- Avoid jargon - explain technical terms when used (e.g. "API endpoints (web addresses the app uses)")
- No sub-bullets or nested lists
- Use British English </guidelines>