From ac-artifact-workflow
Creates and maintains walkthrough.md artifact summarizing implemented system by architecture layers from todo.md, implementation-plan.md, and conversation. Useful in artifact-driven development.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ac-artifact-workflow:walkthrough-creatorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are maintaining the **Walkthrough artifact** (`walkthrough.md`) for an artifact-driven development workflow.
You are maintaining the Walkthrough artifact (walkthrough.md) for an artifact-driven development workflow.
The Walkthrough documents what was built—a clear summary of the resulting system organized by architecture, not by task sequence. It serves as proof of completion and a reference for the finished work.
.artifacts/bld-<project-slug>/todo.md for completed tasks.artifacts/bld-<project-slug>/implementation-plan.md for planned architectureCreate/update .artifacts/bld-<project-slug>/walkthrough.md as implementation proceeds.
One paragraph summarizing what was accomplished:
I've successfully built a [description of what was built] that [key capabilities]. [Additional context on approach or notable features].
Organize by logical layers or areas (Backend Services, Frontend Components, Configuration, etc.).
For each component:
1. Component Name (filename.ext)
Brief description of what this component does:
Example:
**1. Weather Provider Integrations** (`weatherProviders.js`)
Integrated three weather APIs with data normalization:
- **OpenWeatherMap**: 3-hour interval forecasts
- **Open-Meteo**: High-resolution hourly forecasts (no API key required)
- **WeatherAPI.com**: 14-day hourly forecasts
Each provider's data is normalized to a standard format with:
- Temperature (°C)
- Feels-like temperature
- Precipitation amount and probability
Use tables for structured information:
| Endpoint | Method | Description |
|---|---|---|
/api/random-location | GET | Generate random coordinates |
/api/weather?lat={lat}&lon={lon} | GET | Get aggregated forecast |
Quick instructions to start/use the implementation:
npm install
npm run dev
# Open http://localhost:3000
Any constraints, deferred features, or edge cases not handled.
---
status: in-progress
created: <timestamp>
updated: <timestamp>
---
# <Project Name> - Walkthrough
## Overview
<One paragraph summary of what was accomplished>
## What Was Built
### <Layer/Area Name>
**1. Component Name** (`filename.ext`)
Description:
- Point one
- Point two
**2. Component Name** (`filename.ext`)
Description:
- Point one
- Point two
### <Another Layer/Area>
...
## API Reference
| Endpoint | Method | Description |
|----------|--------|-------------|
| ... | ... | ... |
## How to Run
...
## Known Limitations
...
Update incrementally as major components are completed—don't wait until the end. Each significant piece of functionality should be documented when it's working.
IMPORTANT: Every time you modify walkthrough.md, update the updated: field in the frontmatter with the current timestamp.
When implementation is complete:
status: completeWhen presenting, always:
📄 .artifacts/bld-<project-slug>/walkthrough.mdnpx claudepluginhub alteredcraft/claude-code-plugins --plugin ac-artifact-workflowGenerates API documentation, architecture diagrams (C4/Mermaid), READMEs, code comments, and technical writing from codebases.
Audits existing docs and generates full project documentation in docs/ including architecture.md, getting-started.md, development.md, API refs, and ADRs. For onboarding and context sharing.
Creates implementation-plan.md artifact from approved todo.md tasks, structuring project summary, user review decisions, proposed file changes by layer, and testing strategy.