Skip to content

hfadhlullah/Tanya / .agent/skills/proposal

proposal

Verified

Create a new change proposal with spec deltas

Guardrails

  • Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
  • Keep changes tightly scoped to the requested outcome.
  • Refer to prompter/AGENTS.md (located inside the prompter/ directory—run ls prompter if you don't see it) if you need additional Prompter conventions or clarifications.
  • Identify any vague or ambiguous details and ask the necessary follow-up questions before editing files.
  • Do not write any code during the proposal stage. Only create design documents (proposal.md, tasks.md, design.md, and spec deltas). Implementation happens in the apply stage after approval.

Steps

  1. Review prompter/project.md, run prompter list and prompter list --specs, and inspect related code or docs (e.g., via rg/ls) to ground the proposal in current behaviour; note any gaps that require clarification.
  2. Choose a unique verb-led change-id and scaffold proposal.md, tasks.md, and design.md (when needed) under prompter/changes/<id>/.
  3. Map the change into concrete capabilities or requirements, breaking multi-scope efforts into distinct spec deltas with clear relationships and sequencing.
  4. Capture architectural reasoning in design.md when the solution spans multiple systems, introduces new patterns, or demands trade-off discussion before committing to specs.
  5. Draft spec deltas in changes/<id>/specs/<capability>/spec.md (one folder per capability) using ## ADDED|MODIFIED|REMOVED Requirements with at least one #### Scenario: per requirement and cross-reference related capabilities when relevant.
  6. Draft tasks.md as an ordered list of small, verifiable work items that deliver user-visible progress, include validation (tests, tooling), and highlight dependencies or parallelizable work.
  7. Validate with prompter validate <id> --strict and resolve every issue before sharing the proposal.

Reference

  • Use prompter show <id> --json --deltas-only or prompter show <spec> --type spec to inspect details when validation fails.
  • Search existing requirements with rg -n "Requirement:|Scenario:" prompter/specs before writing new ones.
  • Explore the codebase with rg <keyword>, ls, or direct file reads so proposals align with current implementation realities.
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: 197kUpdated 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