- Standardize all workflow descriptions to follow format: [short description]. Use when the user says 'explicit action phrase' or 'another phrase'
- Remove verbose descriptions in favor of concise summaries with explicit trigger phrases
- Use max 2 phrases per workflow to minimize context and false positives
- Phrases are explicit actions (e.g., "lets create", "run X") not questions
- No slash commands in descriptions - users invoke via /name directly
- Rename qa/automate to qa-generate-e2e-tests for clarity
- Update various core tasks and workflows
Add an optional also_consider parameter that allows callers to pass
domain-specific areas to keep in mind during review. This gently nudges
the reviewer toward specific concerns without overriding normal analysis.
Testing showed:
- Specific items steer strongly (questions get directly answered)
- Domain-focused items shift the lens (e.g., security focus = deeper security findings)
- Vague items have minimal effect (similar to baseline)
- Single items nudge without dominating
- Contradictory items handled gracefully
Includes test cases with sample content and 10 configurations to validate
the parameter behavior across different use cases.
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: Brian <bmadcode@gmail.com>
* feat: add editorial review tasks for structure and prose
Add two complementary editorial review tasks:
- editorial-review-structure.xml: Structural editor that proposes cuts,
reorganization, and simplification. Includes 5 document archetype models
(Tutorial, Reference, Explanation, Prompt, Strategic) for targeted evaluation.
- editorial-review-prose.xml: Clinical copy-editor for prose improvements
using Microsoft Writing Style Guide as baseline.
Both tasks support humans and llm target audiences with different principles.
* fix: add content-sacrosanct guardrail to editorial review tasks
Both editorial review tasks (prose and structure) were missing the key
constraint that reviewers should never challenge the ideas/knowledge
themselves—only how clearly they are communicated. This restores the
original design intent.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* fix: align reader_type parameter naming across editorial tasks
Prose task was using 'target_audience' for the humans/llm optimization
flag while structure task correctly separates 'target_audience' (who
reads) from 'reader_type' (optimization mode). Aligns to reader_type.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: Brian <bmadcode@gmail.com>
Brian Madison
Brian Madison
Alex Verkhovsky