What problem does it solve?
Editing feedback from editors and authors often arrives in unstructured form, making it hard to track, classify, and reuse for future revisions.
This skill provides a standardized workflow to categorize feedback, persist it as structured records in a project-specific log, and surface actionable items for editorial QA.
Core Features & Use Cases
- Classification: automatically categorize feedback into types like correction, revision, direction, or question, and assign an impact level.
- Persistence & Traceability: store entries in .editorial/YYYY-MM.jsonl with metadata about source, type, scope, and status, enabling audit trails.
- Editorial Rule Promotion: promote relevant feedback to EDITORIAL.md to codify project-wide rules, with provenance markers for traceability.
- Use Case: during a manuscript review, paste editor or author notes; the skill logs each item for later consolidation and rule extraction.
Quick Start
Paste editorial feedback text into the system and run the edi-feedback skill to classify and persist it in your project’s editorial log.
