Work-Item Artifact Directories

Organize project documentation into structured per-item directories under .sweetclaude/work/.

6|3|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/carson-sweet/sweetclaude --skill work-item-artifact-directories
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Work-Item Artifact Directories
Source: https://github.com/carson-sweet/sweetclaude/tree/main/skills/work-item-artifacts
Command: npx skills add https://github.com/carson-sweet/sweetclaude --skill work-item-artifact-directories

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) components.

What problem does it solve?

This skill solves the fragmentation of project documentation by ensuring that all design docs, plans, contracts, and decision logs related to a specific story, epic, or milestone are co-located in a single, predictable directory structure.

Core Features & Use Cases

  • Automated Organization: Automatically creates and manages directories under .sweetclaude/work/ for every work item.
  • Backfill Capability: Scans existing project files to identify and link legacy artifacts into the new structure using symlinks.
  • Status Monitoring: Provides a quick health check to identify broken symlinks or missing artifact directories.

Quick Start

Run the onboard command to initialize the artifact directory structure and backfill existing project files.

Frequently Asked Questions about Work-Item Artifact Directories

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

FAQPage Schema
How do I organize scattered project documentation into per-item directories?

Organizing project documentation into per-item directories is handled by automatically creating structured folders under .sweetclaude/work/ for every story, epic, or milestone to co-locate related artifacts. This centralizes design docs, plans, and contracts into a predictable structure.

Can I backfill existing legacy files into a new artifact directory structure?

Backfilling legacy files into the new artifact structure is supported by a scanner that identifies existing project files and links them using symlinks. This connects your current documentation to the newly created per-item directories without duplicating data.

What is the best way to verify link integrity for project artifacts across milestones?

Verifying link integrity for project artifacts is performed through a health check that identifies broken symlinks or missing artifact directories. This status monitoring ensures your documentation structure remains intact across stories, epics, and milestones.

Do I need Python 3 to manage work-item artifact directories?

Python 3 is required to execute the backfill scanner and directory management scripts for work-item artifact directories. The scripts rely on Python to automate the organization and linking of project files within the .sweetclaude/work/ path.

How does symlink management work when centralizing project artifacts?

Symlink management works by scanning existing project files and creating symbolic links that point legacy artifacts into the centralized directory structure. This allows backfilling without moving original files, maintaining both the new structure and existing file paths.

What types of project artifacts should be co-located for epics and stories?

Project artifacts that should be co-located for epics and stories include design docs, plans, contracts, and decision logs. Co-locating these items in a single directory ensures all documentation related to a specific work item is predictable and accessible.