Managing Timecard

Time tracking automation eliminates manual logging by using simple command-line punches. The Managing Timecard Skill logs work events instantly via /dakoku commands (in, out, break), storing records organized by month in structured formats, so you maintain accurate attendance without effort.

Yes, command-line time tracking works through the /dakoku command interface. Execute /dakoku with in, out, break, list, or month parameters to punch in/out, log breaks, and review daily or monthly attendance records directly from your terminal.

Monthly work hours reports are generated by executing /dakoku month to summarize all punches for the current month. The Skill produces clean, formatted summaries of your attendance and work hours, ready for review or submission without manual reconstruction.

Time source fallback handles failures by prioritizing the TIME MCP server, then your now alias, then local date as backup. If punching fails, the Skill suggests updating your .zshrc now alias or provides error guidance to restore time logging capability.

Timecard records are stored automatically in _docs/timecard/YYYY/MM as both Markdown and JSON files organized by year and month. This structure keeps attendance history organized and accessible for review or export without manual file management.

Minimal setup is required to begin time tracking. The Skill works with your system's time source and optional now alias; if the now alias isn't configured, it falls back to the TIME MCP server or local date, so you can start punching in immediately.