feat: tool scaffold and structured requirement intake#82
Merged
Conversation
npm run new:tool -- <domain> <yuque_tool_name> creates a gate-passing tool stub and placeholder test for new domains, prints a paste-ready snippet for existing domains without touching their files, rejects duplicate tool names, and always prints the remaining delivery checklist mirroring docs/workflows/add-tool.md. Turns the add-tool recipe from a document agents must follow into a procedure the harness executes. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
New Tool Request issue template captures a deliverable spec (tool name, upstream endpoint, access type, parameter table, acceptance criteria, out-of-scope check) so agents can implement directly from the issue. Feature Request gains an optional acceptance criteria field. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Stacked on #80 (which is stacked on #79 — merge in order). Third batch of harness building: converts the two remaining judgment-heavy spots in the delivery pipeline into procedure.
npm run new:tool -- <domain> <yuque_tool_name>: scaffolds a gate-passing tool stub + placeholder test for new domains; for existing domains prints a paste-ready snippet without touching the file; rejects duplicate tool names and malformed args; always prints the remaining delivery checklist mirroringdocs/workflows/add-tool.md. The add-tool recipe goes from "document the agent must follow" to "procedure the harness executes".docs/capability-scope.md. Feature Request gains an optional acceptance criteria field.Test plan
src/tools/demo.ts+tests/tools/demo.test.ts; fullnpm run checkgreen with generated stubs in place (185 tests)git statusconfirms no file modifiedyuque_get_doc): rejected with file locationDemo): rejected with usage guidance🤖 Generated with Claude Code