skills.rest
mohamedgshoaib
mohamedgshoaibCOMMUNITY
Explore all skills by this author →
Website𝕏@mohamedgshoaibGitHub

wrap-up

Append progress, decisions, and blockers to date-stamped session log files.

5|Updated Jan 20, 2026
Search Tags:#documentation#productivity#logging#session management#tracking
One-click install
npx skills add https://github.com/mohamedgshoaib/reway --skill wrap-up-mohamedgshoaib
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wrap-up
Source: https://github.com/mohamedgshoaib/reway/tree/main/.agents/skills/wrap-up
Command: npx skills add https://github.com/mohamedgshoaib/reway --skill wrap-up-mohamedgshoaib

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of fragmented work documentation by providing a structured, consistent way to log session outcomes, architectural decisions, and active blockers.

Core Features & Use Cases

  • Automated Session Logging: Maintains a chronological record of work sessions in a standardized format.
  • Decision Tracking: Captures irreversible architectural choices to prevent knowledge loss.
  • Blocker Management: Tracks and resolves project impediments with clear status updates.
  • Use Case: At the end of a long coding session, use this skill to automatically append your progress, key decisions, and remaining blockers to your daily session file.

Quick Start

Invoke the wrap-up skill to log your current session progress and update the active blockers list for today.

Frequently Asked Questions about wrap-up

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize session logs to track development progress?▼

You can standardize session logs by appending progress, decisions, and blockers to date-stamped files. This enforces a strict structure to maintain consistent record-keeping and project continuity in development environments.

What's the best way to document irreversible architectural decisions during a work session?▼

The best way to document architectural decisions is to use an automated session logging structure that captures irreversible choices. This prevents knowledge loss by maintaining a chronological record of your work.

Do I need a specific directory structure to automate session logging?▼

Yes, automated session logging requires access to the spec/sessions/ directory. You also need the SESSION_TEMPLATE.md file to maintain the strict, verified logging structure required for consistent records.

How do I track and manage project blockers at the end of a coding session?▼

You can track project blockers by appending them to date-stamped log files at the end of your session. This blocker management approach provides clear status updates to facilitate project accountability.

Why does maintaining consistent record-keeping help with project continuity?▼

Maintaining consistent record-keeping helps project continuity by solving fragmented work documentation. Standardized logs ensure that session outcomes and active blockers are always accessible for future reference.

Related Skills

Explore More Software Engineering Skills→
product-on-purposeproduct-on-purpose
527

init-project-jpkb

Initialize JPKB projects with standardized documentation and folder structure.

Official
Basic
whjelmarwhjelmar

Memory Plan

Create, update, and track multi-session project implementation plans.

Community
Intermediate
andreadellacorteandreadellacorte
5

groove

Manage engineering workflows with automated task tracking across beans, linear, or GitHub backends.

Community
Advanced
BrandondaymdrBrandondaymdr
1

session-closeout

Audit git state, update documentation, and capture architectural decisions at session end.

Community
Advanced