spec-writing
Specification Writing Skill
Overview
Transform gathered requirements and codebase context into a comprehensive, actionable specification document. The spec is the contract between planning and implementation.
Core principle: Synthesize context into actionable spec. No user interaction needed during writing.
When to Use
Always:
- After requirements gathering is complete
- When you have codebase context available
- Before implementation planning begins
Exceptions:
- Simple changes that don't need formal specs
More from oimiragieo/agent-studio
gcloud-cli
Google Cloud CLI operations and resource management
965pyqt6-ui-development-rules
PyQt6 desktop GUI development rules -- signal/slot architecture, QSS theming, QThread concurrency, layout management, and cross-platform rendering. Enforces MVC separation and responsive UI patterns.
570filesystem
File system operations guidance - read, write, search, and manage files using Claude Code's built-in tools.
360chrome-browser
Browser automation with two integrations - Chrome DevTools MCP (always available, performance tracing) and Claude-in-Chrome extension (authenticated sessions, GIF recording). Use DevTools for testing/debugging, Claude-in-Chrome for authenticated workflows.
303slack-notifications
Slack messaging, channels, and notifications - send messages, manage channels, interact with users, upload files, and add reactions. Use for team communication, incident notifications, and workflow alerts.
244context-compressor
Compress large context before reasoning to reduce token usage while preserving evidence. Use this whenever the user mentions huge files, long prompts, RAG payloads, prompt caching, expensive sessions, codebase context, chat history compaction, or wants the same answer quality with fewer tokens.
146