davepoon/buildwithclaude / plugins/agents-uc-taskmanager/skills/sdd-pipeline
sdd-pipeline
Verified| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 716 B |
| references/agent-flow.md | markdown | 10.5 KB |
| references/context-policy.md | markdown | 3.0 KB |
| references/file-content-schema.md | markdown | 5.5 KB |
| references/shared-prompt-sections.md | markdown | 7.7 KB |
| references/work-activity-log.md | markdown | 1.9 KB |
| references/xml-schema.md | markdown | 5.9 KB |
references/work-activity-log.md
View on GitHub# Work Activity Log
Defines the rules for each agent to record WORK progress in the `works/{WORK_ID}/work_{WORK_ID}.log` file.
---
# 1. Stages and Log Content
* On first execution: The received prompt message** Content of the prompt message received at agent startup (Required)
* On Callback invocation: Called Callback URL, success status, Payload, Response (Required)
* During work: Work items and work content
* On task completion: The prompt message sent to other agents** Content of the prompt message received at agent startup (Required)
## log_work Method
**Do NOT use Bash** for activity log writes. Use the `Write` tool (or `Edit` tool to append).
Format each log entry as:
```
[YYYY-MM-DDTHH:MM:SS]_AGENT_STAGE_description
```
Example: to log an INIT stage, use the **Write** tool to append to `works/{WORK_ID}/work_{WORK_ID}.log`:
```
[2026-03-28T14:30:00]_SPECIFIER_INIT_WORK-09 created — Execution-Mode: direct
```
→ **Bash command rules: see `shared-prompt-sections.md` § 13**
---
## STAGE Table
| STAGE | Timing | Description Example |
|-------|--------|---------------------|
| `INIT` | After WORK_ID determined | `WORK-NN created — Execution-Mode: direct/pipeline/full` |
| `REF` | After STARTUP references | `References: CLAUDE.md, .agent/router_rule_config.json, agents/file-content-schema.md` |
| `PLAN` | After PLAN.md + TASK files created | `PLAN.md, TASK-00.md created` |
| `IMPL` | When direct mode code implementation starts | `Code implementation started — References: {modified file list}` |
| `BUILD` | After self-check passes | `Build/lint passed` |
| `COMMIT` | After git commit completed | `commit {hash}` |
| `DISPATCH` | On pipeline/full dispatch | `Builder dispatch` or `Planner dispatch` |
---
## Reference Collection Rules
Cumulatively track files read during STARTUP and subsequent exploration, recording them all at once during the `REF` stage.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |