Skip to content

refactor(create-expert): simplify verbose descriptions in delegates#387

Merged
FL4TLiN3 merged 2 commits intomainfrom
refactor/377-simplify-descriptions
Jan 3, 2026
Merged

refactor(create-expert): simplify verbose descriptions in delegates#387
FL4TLiN3 merged 2 commits intomainfrom
refactor/377-simplify-descriptions

Conversation

@FL4TLiN3
Copy link
Contributor

@FL4TLiN3 FL4TLiN3 commented Jan 3, 2026

Summary

Simplifies expert descriptions to focus on capability rather than input/output details.

Changes

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

Per docs/making-experts/README.md, description should answer "what can I ask for?" - input/output details belong in instruction.

Closes #377

Test plan

  • CI passes
  • No behavior changes expected

Note

Focuses descriptions on expert capabilities, removing input/output details. No logic or behavior changes.

  • Simplifies description fields for property-extractor, ecosystem-builder, integration-manager, functional-manager, usability-manager, and expert-tester in create-expert-toml.ts
  • Adds changeset entry refactor-377-simplify-descriptions.md (patch for create-expert)

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

Simplify expert descriptions to focus on capability, not input/output details:

- property-extractor: Remove "Provide requirements text. Returns..."
- ecosystem-builder: Remove "Provide extracted properties..."
- integration-manager: Remove "Provide ecosystem info and properties..."
- functional-manager: Remove "Provide properties and ecosystem..."
- usability-manager: Remove "Provide ecosystem and properties..."
- expert-tester: Remove "Provide stage, expert name, properties..."

Per docs/making-experts/README.md, description should tell delegators
"what can I ask for?" - input/output details belong in instruction.

Closes #377

🤖 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 9b7d626 into main Jan 3, 2026
7 checks passed
@FL4TLiN3 FL4TLiN3 deleted the refactor/377-simplify-descriptions branch January 3, 2026 07:44
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: simplify verbose descriptions in create-expert delegates

1 participant