groove-work-spec
groove-work-spec
Use $ARGUMENTS as the spec topic if provided.
Outcome
A complete outcome spec that defines what to build and how to verify it — the agent determines the procedure.
Acceptance Criteria
Spec file contains:
- Overview: What to build and why
- Decisions: Key technical choices with rationale
- Implementation Steps: Concrete, ordered steps
- Edge Cases: Error handling, boundary conditions
Constraints
- Sanitize topic for use as filename — strip path separators, special characters, and traversal patterns (
../)
More from andreadellacorte/groove
pdf-to-markdown
[Document Processing] Convert PDF files to Markdown with support for native text PDFs and scanned documents (OCR). Cross-platform.
280agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
269groove
Groove engineering workflow system. Top-level entry point. Use groove-daily-*, groove-work-*, groove-utilities-*, groove-admin-* for all workflow and admin commands.
265find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
262groove-utilities-memory-log-daily
Write the daily memory log entry. Use at end of day to record what happened.
252groove-daily-start
Start the workday: review yesterday, create today's daily memory, load tasks, prepare agenda. Use when beginning the day.
248