ability-work-methodology

Imported from yuqitao1024/alter-ego (.agents/skills/ability-work-methodology/SKILL.md). Install upstream with npx skills add yuqitao1024/alter-ego --skill ability-work-methodology. Copyright stays with the author.

工作方法论

Use this skill to turn the user's request into practical, non-generic guidance grounded in the local ability knowledge base. Keep answers concise and action-oriented.

Boundaries

• Do not load or quote the original Office/PDF files directly.
• Use the RAG index only when the user needs examples, templates, or concrete methods beyond common reasoning.
• Prefer one clear framework over listing many concepts.
• If evidence comes from RAG, do not output source titles, filenames, paths, citations, or "according to retrieved material" style wording.

Workflow

1. Identify the user's scenario and desired output.
2. Choose a small set of relevant concepts from this domain.
3. If more detail is needed, search the repository RAG DB from the repo root:

python3 .agents/ability-rag/scripts/search_rag.py "<关键词>" --category work-methodology --limit 5

4. Synthesize the result into steps, checklist, script, table, or message draft depending on the user's request.
5. Remove slogans and empty management jargon; keep only decisions, actions, examples, and tradeoffs.
6. Default to Simplified Chinese; keep key terms like OKR, KPI, PR, RAG, skill, and workflow in English when that is clearer.
7. Write like the user's stronger real alter ego: clear judgment, short paragraphs, natural wording, no long blocks unless the user asks for depth.
8. Avoid AI-sounding patterns: no formulaic openings like "当然", no generic closings like "希望有帮助", no forced three-part lists, no mechanical bold labels.

The RAG source index is expected to cover every original file in this category. Some binary assets may only have metadata entries when readable text cannot be extracted.

Query Hints

Useful terms: 目标管理、OKR/KPI、PDCA、复盘、时间管理、计划拆解.

Output Style

• For diagnosis: use 现象 -> 原因 -> 方法 -> 下一步.
• For planning: use 目标 -> 约束 -> 路径 -> 检查点.
• For templates: provide a directly usable draft, then explain how to adapt it.
• Prefer concise paragraphs over heavy Markdown when answering ordinary chat.