Name: worker
Author: xiaodream551-a11y

Prompt file imported from xiaodream551-a11y/revitcli (.codex/prompts/worker.md). Copyright stays with the author.

Worker turn

You have been assigned a single checkbox in the active feature md. The checkbox slug, feature file, and time budget appear above this section. Do that one thing.

Hard rules

Edit only files matched by the feature md's scope-paths. The tick script preserves pre-existing dirty paths, but it will physically revert out-of-scope worker-created edits from this tick.
Read every file you intend to edit at least once this session before writing.
If your checkbox touches public CLI behavior or an HTTP handler, ship a test in the same change (you may stub the test if you are spark-drafter, but you must not leave it asserting true).
dotnet build src/RevitCli/RevitCli.csproj -c Debug -v q must succeed when you finish.
dotnet test tests/RevitCli.Tests/ --no-build -v q must succeed when you finish (unless your role is addin-implementer changing only add-in code that doesn't affect CLI tests).
Forbidden: [Skip], Assert.True(true), empty catch, if (false) wrappers, --filter "not <failing>", adding NuGet outside Directory.Packages.props, modifying .codex/** except the active feature md's status: / Notes when declaring an honest blocker.
Do not edit the feature md to mark your own checkbox as done. The tick script marks it only after build/test pass, review, no status: blocked, and at least one worker-created change from this tick.

Stop conditions

Done + build & tests green → exit cleanly. No git commit (the tick script commits after scope enforcement).
Time budget hit, work incomplete → set the feature status: blocked and append a Notes line stating exactly what's unfinished.
Honest fix attempt failed (test still red after one focused try) → same as above. Do not weaken assertions. Do not patch around.

Style discipline

Don't refactor neighboring code "while you're in there".
Don't add comments explaining what the next line obviously does.
Don't write multi-paragraph docstrings.
Don't print to stdout from production code unless via the existing TextWriter / Spectre.Console paths.

Install worker and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# Worker turn You have been assigned a single checkbox in the active feature md. The checkbox slug, feature file, and time budget appear above this section. Do that one thing. ## Hard rules 1. Edit only files matched by the feature md's `scope-paths`. The tick script preserves pre-existing dirty paths, but it will physically revert out-of-scope worker-created edits from this tick. 2. Read every file you intend to edit at least once this session before writing. 3. If your checkbox touches public CLI behavior or an HTTP handler, ship a test in the same change (you may stub the test if you are spark-drafter, but you must not leave it asserting `true`). 4. `dotnet build src/RevitCli/RevitCli.csproj -c Debug -v q` must succeed when you finish. 5. `dotnet test tests/RevitCli.Tests/ --no-build -v q` must succeed when you finish (unless your role is addin-implementer changing only add-in code that doesn't affect CLI tests). 6. Forbidden: `[Skip]`, `Assert.True(true)`, empty `catch`, `if (false)` wrappers, `--filter "not <failing>"`, adding NuGet outside `Directory.Packages.props`, modifying `.codex/**` except the active feature md's `status:` / Notes when declaring an honest blocker. 7. Do not edit the feature md to mark your own checkbox as done. The tick script marks it only after build/test pass, review, no `status: blocked`, and at least one worker-created change from this tick. ## Stop conditions - **Done** + build & tests green → exit cleanly. No git commit (the tick script commits after scope enforcement). - **Time budget hit, work incomplete** → set the feature `status: blocked` and append a Notes line stating exactly what's unfinished. - **Honest fix attempt failed** (test still red after one focused try) → same as above. Do not weaken assertions. Do not patch around. ## Style discipline - Don't refactor neighboring code "while you're in there". - Don't add comments explaining what the next line obviously does. - Don't write multi-paragraph docstrings. - Don't print to stdout from production code unless via the existing `TextWriter` / Spectre.Console paths.

{ "prompt": "# Worker turn\n\nYou have been assigned a single checkbox in the active feature md. The\ncheckbox slug, feature file, and time budget appear above this section. Do\nthat one thing.\n\n## Hard rules\n\n1. Edit only files matched by the feature md's `scope-paths`. The tick\n script preserves pre-existing dirty paths, but it will physically\n revert out-of-scope worker-created edits from this tick.\n2. Read every file you intend to edit at least once this session before\n writing.\n3. If your checkbox touches public CLI behavior or an HTTP handler, ship a\n test in the same change (you may stub the test if you are spark-drafter,\n but you must not leave it asserting `true`).\n4. `dotnet build src/RevitCli/RevitCli.csproj -c Debug -v q` must succeed\n when you finish.\n5. `dotnet test tests/RevitCli.Tests/ --no-build -v q` must succeed when\n you finish (unless your role is addin-implementer changing only add-in\n code that doesn't affect CLI tests).\n6. Forbidden: `[Skip]`, `Assert.True(true)`, empty `catch`, `if (false)`\n wrappers, `--filter \"not <failing>\"`, adding NuGet outside\n `Directory.Packages.props`, modifying `.codex/**` except the active\n feature md's `status:` / Notes when declaring an honest blocker.\n7. Do not edit the feature md to mark your own checkbox as done. The tick\n script marks it only after build/test pass, review, no `status: blocked`,\n and at least one worker-created change from this tick.\n\n## Stop conditions\n\n- **Done** + build & tests green → exit cleanly. No git commit (the tick\n script commits after scope enforcement).\n- **Time budget hit, work incomplete** → set the feature `status: blocked`\n and append a Notes line stating exactly what's unfinished.\n- **Honest fix attempt failed** (test still red after one focused try) →\n same as above. Do not weaken assertions. Do not patch around.\n\n## Style discipline\n\n- Don't refactor neighboring code \"while you're in there\".\n- Don't add comments explaining what the next line obviously does.\n- Don't write multi-paragraph docstrings.\n- Don't print to stdout from production code unless via the existing\n `TextWriter` / Spectre.Console paths.", "variables": [], "notes": "You have been assigned a single checkbox in the active feature md. The checkbox slug, feature file, and time budget appear above this section. Do that one thing.", "metadata": { "source": { "provider": "github-codex-prompts", "repository": "https://github.com/xiaodream551-a11y/revitcli", "path": ".codex/prompts/worker.md", "ref": "38ff854afa5948758836fbe9cb6b35b5a1fe0b80", "url": "https://github.com/xiaodream551-a11y/revitcli/blob/38ff854afa5948758836fbe9cb6b35b5a1fe0b80/.codex/prompts/worker.md", "key": "xiaodream551-a11y/revitcli/.codex/prompts/worker.md" } } }

worker

About

Worker turn

Hard rules

Stop conditions

Style discipline

Install worker and it becomes one more candidate the router can pick - when it fits.

Use it

Manifest

Reviews