Skip to content

fix: optimise glossary command for specificity and actionability#217

Closed
tractorjuice wants to merge 1 commit intomainfrom
feat/optimise-glossary-command
Closed

fix: optimise glossary command for specificity and actionability#217
tractorjuice wants to merge 1 commit intomainfrom
feat/optimise-glossary-command

Conversation

@tractorjuice
Copy link
Copy Markdown
Owner

Summary

  • Autoresearch-optimised the /arckit:glossary command prompt over 7 iterations, improving output quality from 7.6 → 9.2 (21% improvement)
  • Definitions are now project-contextualised instead of generic textbook definitions
  • Added Terminology Consistency Notes and Usage Guide sections

Changes

Change Before After
Definitions Generic textbook style Project-contextualised ("In this project, zero-trust means...")
Cross-references Implicit via bold formatting Explicit "See also: Term" format
Term count No minimum specified Minimum 50 terms required
Organization Single flat table Category sub-sections with separate table headers
Consistency No consistency tracking Terminology Consistency Notes section with canonical terms
Actionability No usage guidance Usage Guide with referencing conventions, update triggers, term proposal process

Autoresearch Results

iter 0: 7.6 baseline                                              KEEP
iter 1: 8.0 project-contextualised definitions + See also refs    KEEP  
iter 2: 8.8 50+ terms + categorised sections + Usage Guide        KEEP
iter 3: 9.2 Terminology Consistency Notes                         KEEP

4 keeps, 3 discards across 7 iterations. Converter run included — all 7 distribution formats updated.

Test plan

  • Run /arckit:glossary 001 in a test repo with STKE and PRIN artifacts
  • Verify definitions include project context ("In this project...")
  • Verify "See also:" cross-references are present
  • Verify glossary organised into category sub-sections (not single table)
  • Verify Terminology Consistency Notes section identifies variant terms
  • Verify Usage Guide section present with referencing conventions

🤖 Generated with Claude Code

Autoresearch-optimised the glossary command prompt (7 iterations, 7.6→9.2):

- Require project-contextualised definitions ("In this project...")
  instead of generic textbook definitions
- Add explicit "See also: **Term**" cross-reference format
- Require minimum 50 terms for comprehensive coverage
- Organize glossary into category sub-sections with separate tables
- Add Terminology Consistency Notes section for standardising
  variant terms across artifacts (with canonical term guidance)
- Add Usage Guide section explaining how to reference the glossary,
  when to update it, and how to propose new terms

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@tractorjuice
Copy link
Copy Markdown
Owner Author

Superseded by #265 (combined autoresearch PR for all 48 commands)

@tractorjuice tractorjuice deleted the feat/optimise-glossary-command branch March 27, 2026 17:39
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.

1 participant