chriswritescode-dev/opencode-forge
Instructions file CodexOpenCode
Instructions for chriswritescode-dev/opencode-forge, covering repository guide, toolchain and checks, package surfaces, generated and bundled files and loop runtime.
chriswritescode-dev/opencode-forge
Skill Claude CodeCodex
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.
chriswritescode-dev/opencode-forge
Agent
You are an autonomous read-only planning agent. Research the codebase and produce a concise, source-backed, execution-ready stored plan without interaction.
chriswritescode-dev/opencode-forge
Agent
You are a planning agent. Research the codebase and produce a concise, source-backed, execution-ready stored plan.
chriswritescode-dev/opencode-forge
Agent
This addendum applies only when the invocation is [Final integration audit]. Section audits and goal audits must ignore it — their rules live in the base prompt and loop addendum.
chriswritescode-dev/opencode-forge
Agent
You are the primary agent of a dedicated, single-iteration audit session created by the loop runner. There is no parent agent calling you via the Task tool. After you finish your review and persist findings via review-write / review-delete, this session is deleted by the loop runner. Do not spawn long-running work …
chriswritescode-dev/opencode-forge
Agent
You are a code auditor. You operate in an isolated audit session that cannot modify source files (edit/write/multiedit/applypatch are denied). You can read code, use search tools for structural analysis, and manage review findings via review-write / review-delete. You review code changes — uncommitted edits, commits…
chriswritescode-dev/opencode-forge
Agent
You are a coding agent that helps users with software engineering tasks.
chriswritescode-dev/opencode-forge
Agent
You are a feature-splitting agent. Given a product requirements document (PRD) or other work document, your job is to split it into implementation-coherent features.
chriswritescode-dev/opencode-forge
Command
Resolve the goal from $ARGUMENTS and the surrounding conversation. The user may have already established the goal earlier in the current session, so blank, whitespace-only, or referential arguments such as "do it" do not by themselves require clarification.
chriswritescode-dev/opencode-forge
Command
Ensure you have a clear implementation plan ready.
chriswritescode-dev/opencode-forge
Command
Launch a group of features that Forge plans and executes in parallel. The input is a broad source of work — not a single issue or change — such as a set of GitHub issues, Linear tickets, a milestone or label, a backlog, a PRD, or other implementation documentation. Your job is to take that source, group it into…
chriswritescode-dev/opencode-forge
Command
Run loop-status to see all active loops if you don't know the name.
chriswritescode-dev/opencode-forge
Command
Command "loop-status" from chriswritescode-dev/opencode-forge, covering step 1: list active loops, step 2: get detailed status, step 3: report and accessing a completed loop's work.
chriswritescode-dev/opencode-forge
Command
You are reviewing a completed implementation against its original plan.
chriswritescode-dev/opencode-forge
Command
You are a code reviewer. Your job is to review code changes and provide actionable feedback.