record-work

Create structured work records with fields for context, decisions, and next actions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jukqaz/stack-pilot --skill record-work
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: record-work
Source: https://github.com/jukqaz/stack-pilot/tree/main/addons/stackpilot-dev-kit/claude/skills/record-work
Command: npx skills add https://github.com/jukqaz/stack-pilot --skill record-work

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create or update a compact operating record to persist work context across sessions and external tools.

Core Features & Use Cases

  • Identify the record type (opportunity, decision, project, task, etc.) and create a structured surface for later reference.
  • Attach an active local task-state to keep owner, summary, checkpoint, next action, and lane context aligned.
  • Capture current state, decision, next action, evidence, and links while leaving source-of-truth data in your external systems.

Quick Start

Use the stack-pilot record command to create or update a project or task record for the current work.

Frequently Asked Questions about record-work

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

FAQPage Schema
How do I preserve work context across sessions when collaborating across multiple tools?

A work record preserves context across sessions by capturing structured fields like type, status, owner, and next_action. It leaves source-of-truth data in external systems while maintaining a compact local reference for cross-tool collaboration.

What is the best way to document a task handoff with decision evidence?

Documenting a task handoff requires capturing the current state, decision, evidence, and handoff details in a structured record. This ensures the receiving owner has the necessary context and linked tools to execute the next action immediately.

Can I use structured records to track project planning and task state?

Yes, you can use structured records to track project planning and task state by applying fields like owner, summary, checkpoint, and lane context. This keeps active local task-state aligned with your broader project goals and external systems.

How do I create a durable record for an opportunity or project decision?

Create a durable record by identifying the record type, such as opportunity or decision, and populating structured fields including title, context, decision, and approvals. Validation and guardrails ensure the captured data remains consistent for later reference.

Does this approach duplicate data from my external linked tools?

No, this approach does not duplicate source-of-truth data from external linked tools. It captures a compact operating record with context, decisions, and next actions, leaving the authoritative data in your original systems to prevent sync conflicts.