create-techspec
Create TechSpec
Translate business requirements into a detailed technical specification.
Required Inputs
- Feature name identifying the
tasks/prd-<name>/directory. - Optional: existing
_prd.mdas primary input. - Optional: existing
_techspec.mdfor update mode.
Workflow
- Gather context.
- Check for
_prd.mdintasks/prd-<name>/. If it exists, read it as the primary input. - If no PRD exists, ask the user for a description of what needs technical specification.
- Read existing ADRs from
tasks/prd-<name>/adrs/to understand decisions already made during PRD creation. - Create
tasks/prd-<name>/adrs/directory if it does not exist. - Spawn an Agent tool call to explore the codebase for architecture patterns, existing components, dependencies, and technology stack.
- If
_techspec.mdalready exists, read it and operate in update mode.
- Check for
More from compozy/looper
create-prd
Creates a Product Requirements Document through interactive brainstorming with parallel codebase and web research. Use when starting a new feature or product, building a PRD, or brainstorming requirements. Do not use for technical specifications, task breakdowns, or code implementation.
3create-tasks
Decomposes PRDs and TechSpecs into detailed, independently implementable task files with enrichment from codebase exploration. Use when a PRD or TechSpec exists and needs to be broken down into executable tasks, or when task files need enrichment with implementation context. Do not use for PRD creation, TechSpec generation, or direct task execution.
3execute-prd-task
Executes one PRD task end-to-end using a provided task file, PRD directory, tracking file paths, and auto-commit mode. Use when a prompt includes a task specification that must be implemented, validated, and reflected in task tracking files. Do not use for PR review batches, generic coding tasks without a PRD task file, or standalone verification-only work.
3fix-reviews
Executes provider-agnostic PR review remediation using existing review round files under tasks/prd-<name>/reviews-NNN/. Use when resolving batched review issues, updating issue/grouped markdown files, implementing fixes, and verifying the result. Do not use for PRD task execution, review export/fetch, or generic coding tasks without review issue files.
1