Skip to content

fix(create-expert): improve description clarity for internal experts#367

Merged
FL4TLiN3 merged 1 commit intomainfrom
fix/352-improve-descriptions
Jan 3, 2026
Merged

fix(create-expert): improve description clarity for internal experts#367
FL4TLiN3 merged 1 commit intomainfrom
fix/352-improve-descriptions

Conversation

@FL4TLiN3
Copy link
Contributor

@FL4TLiN3 FL4TLiN3 commented Jan 3, 2026

Summary

Update descriptions to include input expectations and output format, following docs guidance.

Changes

Expert Before After
property-extractor "Extracts testable properties from user requirements" "Extracts testable properties from user requirements. Provide requirements text. Returns user properties, Perstack properties, usability properties, and external dependencies."
ecosystem-builder "Creates Expert ecosystem (main + demo + setup + doctor)" "Creates Expert ecosystem from properties. Provide extracted properties and requirements. Returns perstack.toml with main, demo, and optionally setup/doctor experts."
integration-manager "Orchestrates coordinated functional and usability testing" "Orchestrates functional and usability testing in parallel. Provide ecosystem info and properties. Returns integration report with scores and recommendations."
functional-manager "Manages all functional PDCA cycles (happy-path, unhappy-path, adversarial)" "Runs happy-path, unhappy-path, and adversarial tests. Provide properties and ecosystem. Returns functional test report with pass/fail counts."
usability-manager "Manages usability PDCA cycle for expert ecosystem" "Tests usability of expert ecosystem (demo, setup, doctor, errors). Provide ecosystem and properties. Returns usability report."
expert-tester "Executes tests and reports property-wise results" "Executes tests against experts. Provide stage, expert name, properties, and test cases. Returns property-wise pass/fail results."

Test plan

  • CI passes

Closes #352

🤖 Generated with Claude Code


Note

Improves clarity of expert descriptions in create-expert by specifying what each expert does, what input to provide, and what output to expect.

  • Updates descriptions for property-extractor, ecosystem-builder, integration-manager, functional-manager, usability-manager, and expert-tester in create-expert-toml.ts
  • Adds .changeset/improve-descriptions.md documenting the patch
  • No functional logic changes; TOML content and instructions remain otherwise the same

Written by Cursor Bugbot for commit fc03a13. This will update automatically on new commits. Configure here.

Update descriptions to include input expectations and output format:

- property-extractor: specify it returns structured properties list
- ecosystem-builder: specify it takes properties and returns TOML
- integration-manager: specify parallel testing and report format
- functional-manager: specify test types and report format
- usability-manager: specify ecosystem tests and report format
- expert-tester: specify required inputs (stage, expert, properties, cases)

Follows docs guidance: "A good description tells potential callers
what this Expert can do, when to use it, and what to include."

Closes #352

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@codecov
Copy link

codecov bot commented Jan 3, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@FL4TLiN3 FL4TLiN3 merged commit 3b61b9e into main Jan 3, 2026
7 checks passed
@FL4TLiN3 FL4TLiN3 deleted the fix/352-improve-descriptions branch January 3, 2026 05:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Refactor: Improve description clarity for create-expert internal experts

1 participant