design-an-interface
Design an Interface
Based on "Design It Twice" from "A Philosophy of Software Design": your first idea is unlikely to be the best. Generate multiple radically different designs, then compare.
Workflow
1. Gather Requirements
Before designing, understand:
- What problem does this module solve?
- Who are the callers? (other modules, external users, tests)
- What are the key operations?
- Any constraints? (performance, compatibility, existing patterns)
- What should be hidden inside vs exposed?
Ask: "What does this module need to do? Who will use it?"
2. Generate Designs (Parallel Sub-Agents)
More from costicapuntaru/agentica
opsx-apply-subagents
Orchestrates dependency-aware parallel subagents for OpenSpec workflows, supporting OPSX commands, legacy openspec commands, and Codex CLI prompt aliases. Use when running /opsx:apply, /openspec:apply, or any opsx command with multiple independent tasks that can be parallelized.
15write-a-prd
Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.
9epic-workflow
End-to-end Epic planning — grill requirements, write a PRD, decompose into GitHub issues with dependencies, and create a feature branch for autonomous implementation. Use when starting a new epic, planning a large feature, or when user says "epic workflow", "plan this feature", or "start a new epic".
8openspec-bugfix
Start a new bugfix using the OpenSpec artifact workflow. Use when the user describes a bug, defect, or unexpected behavior and wants to fix it using a structured approach.
8github-auto-implement
Autonomous GitHub issue implementation — picks the next ready issue, triages it, implements with TDD, and opens a PR targeting the correct branch (default, epic feature branch, or PR-chained dependency branch). Use when running the autobot daemon, implementing GitHub issues autonomously, or starting the auto-implement loop.
8tdd
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
7