lector

Triage project issues into structured plans, requirements, and documentation.

8|Updated Dec 12, 2025

Search Tags:#planning #architecture #documentation #requirements #governance #triage

Ready to run

npx skills add https://github.com/smile13241324/aemacs --skill lector

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lector
Source: https://github.com/smile13241324/aemacs/tree/main/.agents/skills/lector
Command: npx skills add https://github.com/smile13241324/aemacs --skill lector

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams triage incoming issues and convert them into structured plans, requirements, and documentation, reducing ambiguity and accelerating architectural decisions.

Core Features & Use Cases

Issue triage and categorization into duplicates, bugs, features, and needs-info.
Generation of strategic plans, requirements, and documentation without writing implementation code.
Architecture-focused governance for project initiatives within the Æmacs ecosystem.

Quick Start

Triage a submitted issue and generate a strategic plan with requirements and documentation.

Frequently Asked Questions about lector

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I triage project issues to identify duplicates and invalid tickets?▼

Triage project issues by categorizing incoming tickets into duplicates, bugs, features, and needs-info. This process handles vague and invalid tickets to produce consistent outputs, reducing ambiguity and accelerating architectural decisions.

Can I generate strategic plans and requirements without writing implementation code?▼

Yes, you can generate strategic plans, requirements, and documentation without writing implementation code. The tool enforces role boundaries by avoiding code generation and delivering only high-level architectural artifacts.

What is the best way to draft requirements for architecture reviews and backlog triage?▼

Drafting requirements for architecture reviews and backlog triage is best handled by converting incoming issues into structured plans. This approach standardizes requirement drafting across strategic initiatives to ensure consistent architectural governance.

Does this approach to issue triage support high-level architecture governance?▼

Yes, this approach supports architecture-focused governance for project initiatives. It enforces role boundaries by delivering high-level architectural artifacts rather than code, ensuring consistent governance across strategic initiatives.

When should I not use automated triage for project backlog management?▼

You should not use automated triage when you need implementation code instead of high-level artifacts. The tool strictly avoids code generation and focuses solely on delivering structured plans, requirements, and documentation.

How do I convert vague project tickets into structured documentation?▼

Convert vague project tickets into structured documentation by applying issue triage categorization. This process identifies duplicates, bugs, features, and needs-info tickets to produce consistent outputs and accelerate architectural decisions.