Working

Collect, process, and archive daily work across multiple tasks with in/out/log files.

Updated Jan 21, 2026
One-click install
npx skills add https://github.com/terateams/TAES --skill working
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Working
Source: https://github.com/terateams/TAES/tree/main/.github/skills/Working
Command: npx skills add https://github.com/terateams/TAES --skill working

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a unified daily workspace to collect, process, and archive work across multiple tasks, ensuring nothing is lost and every day ends with a clear record.

Core Features & Use Cases

  • Cross-task in/out/log workflow: capture inputs (in.md), execute per task with ICE, and publish outputs (out.md) with permanent logs (log.md) and artifacts.
  • End-of-day cleanup and traceability: daily cleanup ensures accountability and a persistent history.

Quick Start

To start, add items to in.md, run ICE-structured tasks to transform them, move results to out.md, and let important decisions and milestones be appended to log.md. Use artifacts/ to store long-term deliverables.

Frequently Asked Questions about Working

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

FAQPage Schema
How do I manage daily cross-task workflows with a consistent intake and output process?

A daily cross-task workflow collects inputs in in.md, executes tasks using ICE structure, publishes outputs to out.md, and archives decisions in log.md for traceability. This ensures nothing is lost within a 24-hour cycle.

What is the best way to maintain an audit trail for daily task management?

An audit trail for daily task management is maintained by appending important decisions and milestones to log.md during end-of-day cleanup, creating a persistent history and accountability record across multiple tasks.

How do I organize task inputs and outputs across multiple projects in one workspace?

You organize task inputs and outputs by adding items to in.md, processing them through ICE-structured tasks, moving results to out.md, and storing long-term deliverables in an artifacts directory for cross-task coordination.

Can I use this daily workspace for cross-task coordination without external dependencies?

Yes, this daily workspace operates without external dependencies, using markdown files like in.md, out.md, and log.md to guide intake, execution, and archival steps for cross-task coordination.

Does this daily workspace handle long-term deliverables separately from daily logs?

Yes, this daily workspace handles long-term deliverables separately by using an artifacts directory to store them, while log.md maintains the daily history and out.md captures the daily outputs.

When do I need a cross-task daily workspace instead of individual task tracking?

You need a cross-task daily workspace when your day-to-day operations span multiple tasks and require a unified intake, execution, and archival process to ensure consistency and traceability within a 24-hour cycle.