wickedizer

当您需要撰写、改写或赋予内容以人文关怀时，可优先使用此技能。在保留原文含义的同时，去除AI生成的“痕迹”，使输出内容更贴近团队的表达风格：直白、务实、注重行动导向。适用场景如下： - 撰写或改写散文、技术文档、产品需求文档、演示文稿 - 为AI生成的内容注入人文气息，或将文本中的“AI味”淡化 - 创建工作事项（如Jira、Linear、GitHub Issue） - 撰写PR描述、提交信息、ADR - 编写代码注释、文档字符串、README文件

SKILL.md

--- frontmatter

name: wickedizer
description: |
  Use this skill when writing, rewriting, or humanizing content. Removes AI tells while preserving meaning. Aligns output to team voice: direct, practical, action-oriented.

  Use when:
  - Writing or rewriting prose, technical docs, PRDs, slides
  - Humanizing AI-generated content or de-AI-ing text
  - Creating work items (Jira/Linear/GitHub Issues)
  - Drafting PR descriptions, commit messages, ADRs
  - Writing code comments, docstrings, READMEs

Wickedizer: Clear, Credible, Human Writing

You are rewriting for trust and clarity, not for "vibes."

Your job:

•Remove AI-generated tells (fluff, hedging, promo language, chatbot artifacts)
•Preserve meaning, constraints, and domain terms
•Align to team voice: direct, pragmatic, outcome-driven
•NEVER invent facts, citations, names, or numbers

When This Skill Applies

Invoke automatically when:

•Writing or rewriting prose (emails, memos, exec summaries, PRDs, POVs)
•Producing slide text or bullets
•Writing work items (epics/stories/tasks/bugs in Jira, Linear, GitHub Issues, Azure DevOps, etc.)
•Drafting PR descriptions, commit messages, ADRs/RFCs, design docs
•Writing code comments, docstrings, READMEs, runbooks

Non-Negotiables

•Do not change meaning - Preserve commitments, constraints, scope, decisions
•Do not add facts - No invented stats, quotes, names, dates, attributions
•Keep useful structure - Headings, bullets, tables that aid scanning
•Keep terminology stable - Same concept = same name everywhere
•Match medium + audience - Slack ≠ PRD ≠ exec memo

Operating Process

Step 0: Classify the Artifact

Pick ONE: exec-summary | technical-doc | prd-requirements | work-item | email-comms | slide-bullets | code-comments | mixed

→ See refs/artifact-types.md for mode-specific rules.

Step 1: Extract Immutables

Identify and preserve:

•Facts, dates, numbers, names, owners
•Decisions, constraints, scope boundaries
•Domain terms and key nouns
•Acceptance criteria / definitions of done

Step 2: De-AI Pass

Remove:

•Chatbot artifacts ("hope this helps", validation filler)
•Promotional language and significance inflation
•Hedge stacking ("could potentially possibly")
•Vague attributions ("experts say")
•Cadence uniformity (same rhythm every sentence)

→ See refs/de-ai-pass.md for detection patterns.

Step 3: Clarity Pass

•Convert abstract nouns into actions
•Replace vague verbs with specific ones
•Ensure reader can answer: What changed? Why? Who owns it? What's next?

Step 4: Voice Pass

Apply team voice defaults:

•Assertive opening sentence with limited bold
•Scannable structure: short paragraphs, real bullets
•Consistent terms (no synonym cycling)
•Close with next steps / decision points

→ See refs/voice-profile.md for full voice guide.

Step 5: Trust Check

Before output, verify:

• No added facts, citations, names, or stats
• Meaning and constraints preserved
• Structure appropriate for medium
• Output contains at least one: decision, tradeoff, next step, open question, or measurable outcome

→ See refs/failure-modes.md for common problems.

Quick Reference: What to Remove

Pattern	Fix
"Additionally / Furthermore / Moreover" spam	Delete most transitions
"Pivotal / transformative / game-changing"	Remove or prove
"Not just X, but Y" scaffolding	State directly
Rule-of-three when 2 is correct	Use real count
"Experts agree" without naming	Cite or delete
"Hope this helps!"	Delete

Quick Reference: What to Keep

Element	When
Bullets and lists	When they aid scanning
Technical terms	When precise
Numbers and dates	Always (don't generalize)
Named constraints	Always
Scope boundaries	Always

Output Format

Return:

•The rewritten content
•
Optional Change Log (3-8 bullets) if helpful:
- •Removed fluff
- •Clarified claims
- •Preserved constraints
- •Adjusted structure

Flexibility Note

These are defaults, not laws. Override when:

•Source material is intentionally casual or formal
•Audience expects different tone (legal, marketing)
•Context requires adaptation

The goal is credible and specific, not rigid adherence. Situation matters more than rules.

References

Core Process:

•Voice Profile - Tone, sentence structure, ending strong
•De-AI Pass - Detecting and removing AI tells
•Artifact Types - Mode-specific guidance

Principles:

•Structure - Document architecture and organization
•Complexity - KISS, YAGNI, DRY for writing
•Patterns - Reusable templates and structures

Quality:

•Review - Validation checklists by type
•Failure Modes - Common problems and fixes