rankup-work-logging
Logs work progress and yarn validate evidence to keep project documentation and status accurate.
Install
mkdir -p .claude/skills/rankup-work-logging && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15452" && unzip -o skill.zip -d .claude/skills/rankup-work-logging && rm skill.zipInstalls to .claude/skills/rankup-work-logging
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Work tracking + evidence logging for Rankup. Use when updating docs/work (CURRENT, ROADMAP, epics, log) and recording yarn validate evidence to close WPs/epics reproducibly.Key capabilities
- →Update Work Package (WP) and epic statuses.
- →Record validation evidence in the daily log.
- →Update `docs/work/CURRENT.md` to the next unit of work.
- →Mark WP sections as Done/Blocked with notes.
- →Append command(s) executed and PASS/FAIL status to log.
How it works
The skill updates the status of work packages and epics, records validation evidence in a daily log, and updates the `CURRENT.md` file to reflect the next unit of work. It ensures work documentation is reproducible.
Inputs & outputs
When to use rankup-work-logging
- →Update epic status to closed
- →Record yarn validate output
- →Log daily work completion
- →Move CURRENT.md to next task
About this skill
Rankup: Work tracking + evidence logging
Objective
Keep docs/work/** reproducible:
- WPs have clear DoR/DoD
- Validation evidence is recorded
- CURRENT/ROADMAP reflect reality
Trigger / Use when
- You finish a WP or an epic.
- You ran
yarn validateand need to record results. - You need to move CURRENT to the next unit of work.
Minimal workflow
- Update WP/epic status
- Mark WP sections as Done/Blocked with a short note.
- Update epic status if closing.
- Record evidence in the daily log
- Append to
docs/work/log/YYYY-MM-DD.md:- command(s) executed
- PASS/FAIL
- short note about scope
- Update
docs/work/CURRENT.md
- Point to next WP/epic.
- Keep it small and unambiguous.
Evidence format (recommended)
## YYYY-MM-DD
- WP-XXX-YY: <short label>
- yarn validate: PASS
- notes: <1-2 lines>
Done criteria
- Work docs reflect actual repo state.
- Evidence exists for validation gates.
When not to use it
- →When the user does not need to update Rankup work documentation.
- →When the user does not need to record `yarn validate` results.
- →When the user does not need to move `CURRENT.md` to the next unit of work.
Limitations
- →Requires manual update of WP/epic status.
- →Evidence format is recommended but not strictly enforced.
- →Focuses on Rankup-specific work tracking.
How it compares
This skill provides a structured and reproducible way to log work and update project documentation, ensuring clear definitions of done and recorded validation evidence, unlike informal tracking methods.
Compared to similar skills
rankup-work-logging side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| rankup-work-logging (this skill) | 0 | 2mo | No flags | Beginner |
| tbd | 0 | 5mo | Review | Intermediate |
| preserve | 0 | 2mo | Review | Beginner |
| session-handoff | 0 | 3mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
tbd
jlevy
|-
preserve
markwharton
Preserve the most recently approved plan to docs/plans/
session-handoff
Maximumsoft-Co-LTD
Serialize mid-session context into a handoff doc so the next session (or engineer) can resume without cold-start
handoff
hta218
Capture current work context for handoff to another agent/developer. Gathers git state, todos, and modified files into a structured handoff document saved to the related spec folder.
issue-to-requirement
1021ky
GitHub Issue の曖昧な要求を、このプロジェクトで実装可能な要件へ正規化する。機能分類、層別要件、実装スコープ、判定待ち項目を整理し、issue-to-plan へ渡す。
complete-task
Log2n-io
Complete work on a GitHub issue - close issue, update artifacts, prompt for doc updates