Plan 3 binary outcomes per day, hard-stop at 5pm. Branded HTML accountability tracker that fixes the 'AI made me feel behind' problem. Claude Code plugin.
SaferSkills independently audited define-done (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Takes N days of goals from the user, applies the "Define Done" ritual rules, and writes a single self-contained HTML file to 008_Builds/define-done/{YYYY-MM-DD}-define-done.html.
The HTML is designed to live in a browser tab and be checked twice a day:
Triggers:
Ask ONE question if missing:
"What 3 outcomes per day for the next [N] days? Or want me to draft them from your active projects?"
If the user says "draft them" → read 01_Projects/Clients/Active/INDEX.md, 01_Projects/Internal/AY_Automate/AY_AUTOMATE_HQ.md, and 02_Areas/Sales/Pipeline/ for current priorities. Propose 3 outcomes per day, ask for sign-off, then generate.
Before writing the HTML, audit each outcome:
If any outcome fails, rewrite it before generating.
Use the template at templates/tracker-template.html. Replace these markers:
| Marker | What to inject |
|---|---|
{{TITLE}} | e.g. "Week of Jun 10 — Define Done" |
{{START_DATE}} | First day, formatted "Mon · Jun 10" |
{{END_DATE}} | Last day, formatted "Sun · Jun 16" |
{{TODAY_LABEL}} | "Today is Tuesday, Jun 11" (or current day) |
{{DAYS_HTML}} | The repeated day blocks (see template) |
{{NORTH_STAR}} | One sentence: the weekly anchor (e.g. "ship 2 client builds, publish 3 posts") |
{{RITUAL_NOTE}} | Customizable footer note. Default: the 4-line ritual reminder. |
{{BRAND_TAG}} | From ${user_config.brand_name}. Default: DEFINE DONE |
{{SIGNATURE}} | From ${user_config.signature}. Default: DEFINE DONE · MIT LICENSED |
When this skill runs inside the installed plugin, read these env-injected values from ${user_config.*}:
${user_config.brand_name} → {{BRAND_TAG}}${user_config.accent_color} → inject <style>:root{--accent:VALUE}</style> before </head>${user_config.background_color} → inject --bg override the same way${user_config.hard_stop_time} → use in stamps (e.g. 17:00 HARD STOP instead of 5PM HARD STOP)${user_config.outcomes_per_day} → cap N per day; reject extras${user_config.signature} → {{SIGNATURE}}If ${user_config.*} is not available (skill used outside plugin), fall back to template defaults.
For each day, emit a day block:
<div class="day">
<div class="day-head">
<div class="day-name">{{DAY_NAME}}</div>
<div class="day-date">{{DAY_DATE}}</div>
</div>
<ol class="outcomes">
<li><label><input type="checkbox"><span>{{OUTCOME_1}}</span></label></li>
<li><label><input type="checkbox"><span>{{OUTCOME_2}}</span></label></li>
<li><label><input type="checkbox"><span>{{OUTCOME_3}}</span></label></li>
</ol>
<div class="day-foot">
<span class="stamp">5PM HARD STOP</span>
<span class="score" data-day="{{DAY_INDEX}}">0/3</span>
</div>
</div>Save to: 008_Builds/define-done/{YYYY-MM-DD}-define-done.html where {YYYY-MM-DD} = start date.
After writing, screenshot it with vision-verify to confirm it renders. Use viewport 1120x780 for the screenshot.
Return:
These come from the user's CLAUDE.md and from how Claude Code works best:
008_Builds/define-done/
2026-06-10-define-done.html ← N-day tracker
2026-06-10-define-done.png ← screenshot for reviewvision-verify to confirm renderlinkedin-hooks or contentproposal-buildercold-dance or enrichUser: "build my define-done tracker for the next 5 days"
Claude:
008_Builds/define-done/2026-06-10-define-done.html~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.