Skip to content

AlpacaLabsLLC/skills-for-architects / skills/workplan

workplan

Verified

Prepare a proportionate work plan with outcomes, steps, dependencies and acceptance evidence. Use to plan substantial work or coordinate an approved team; a plan-only request does not authorize implementation.

FileKindSize
README.mdmarkdown150 B
SKILL.mdskill md4.8 KB
host-contract.jsonconfig1.7 KB
templates/plan.mdmarkdown2.4 KB

templates/plan.md

View on GitHub
# [Outcome-oriented title]

- **Created:** YYYY-MM-DD
- **Status:** Ready for review
- **Planning mode:** Repository | AEC delivery | General
- **Depth:** Lightweight | Standard | Deep

## Outcome

[What completing this plan will make true.]

## Problem Frame

[Why the work is needed and what currently prevents the outcome.]

## Scope

### Included

- [Included outcome or responsibility]

### Excluded

- [Adjacent work deliberately left out]

## Evidence Reviewed

- [Project-relative source path and relevant heading or stable item ID]
- [Unreadable or malformed path and the limitation it creates]

## Requirements

- **R1 —** [Required capability, constraint, or outcome]

## Known Facts

- [Observed fact with a project-relative source link]

## Assumptions

- **A1 —** [Unverified condition the plan currently relies on]

## Decisions

### D1 — [Decision title]

- **Choice:** [Selected approach]
- **Why:** [Load-bearing rationale]
- **Alternative considered:** [Meaningful rejected alternative]
- **Source:** [Project-relative decision record or other evidence]

## Work Units

### W1 — [Outcome-oriented unit]

- **Produces:** [Artifact or observable result]
- **Depends on:** None | W# | external dependency
- **Covers:** R#
- **Governed by:** D# | None
- **Sources:** [Project-relative links, headings, or stable item IDs that shape this unit]

**Work boundary:**

- [What belongs in this unit]
- [What must remain outside it]

**Verification:**

1. [Specific evidence or behavior that proves the unit is complete]
2. [Applicable edge, failure, coordination, or integration scenario]

## Dependencies and Risks

- [Dependency or risk, its owner/source when known, and consequence]

## Open Questions

- [Execution-time question that does not change the confirmed scope]

## Definition of Done

- [Observable completion condition]
- Every requirement is covered by a completed work unit.
- Required verification evidence has been recorded.

## Execution handoff (when applicable)

Record the requested output, bounded owner assignments, dependencies, exclusive file ownership, integrator and acceptance evidence. State whether the user approved implementation and any useful team. A plan-only request grants neither. Prior exact approval persists; the main harness creates an approved team through real tools.

For durable filing, use confirmed document coordinates and register kind `plan`; a revision names the superseded document ID. An inline plan requires no file.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall