opencode-project-template

Repeatable codebase audit & fix cycle using parallel agent teams. Phases: audit, consolidate, fix, validate. All output stays in docs/.tmp/ (gitignored, never committed). Supports delta-scoped audits via --since=<tag> to review only changed files and their adjacent code paths (cost-effective for continuous use).

Conducts a relentless interview about every aspect of a plan or idea, walking down each branch of the design tree until shared understanding is reached. Invoke with /grill-me before starting any significant design or implementation work.

Converts a PRD (Forgejo issue or local file) into independently executable Forgejo issues organised as vertical slices through integration layers. Invoke with /prd-to-issues <issue-url-or-path>.

Implements a feature or fix using strict red-green-refactor TDD cycles. Confirms interfaces and behaviours before writing any code. Invoke with /tdd <task description>.

Transforms a conversation or idea into a Product Requirements Document (PRD) with user stories, then submits it as a Forgejo issue. Invoke with /write-a-prd when ready to formalise a feature or initiative.

Refresh .abstract.md (L0) and .overview.md (L1) across all subsystems. Diff mode (default) updates only subsystems modified since the last index; regeneration mode rewrites everything. Invoke with /context-update when indexes may be stale, before running the large task planning protocol, or after significant refactors.

Incorporate an insight, protocol, or convention from another agent session into the opencode-project-template. Extracts the pattern, places it in the right template file, and bumps the version. Invoke with /template-update when you have a conversation excerpt or lesson learned that should be codified into the template.

Read-only codebase review using parallel audit agents. Produces consolidated findings and exceptions in docs/.tmp/ without making any code changes.

One-sentence description of what this skill does and when to invoke it via /example-skill.