Academic Paper Drafting Skill
Turn research into published scholarship. From blank page to accepted manuscript.
This skill provides structured workflows for drafting academic papers, with venue-specific guidance for HCI conferences (CHI), business publications (HBR), and academic journals (Cognitive Systems Research, Minds & Machines).
Drafting Philosophy
The Academic Writing Paradox
| Challenge |
Reality |
Strategy |
| "I need to read more first" |
Reading is procrastination |
Write to discover what you don't know |
| "I need the perfect first sentence" |
First drafts are meant to be bad |
Start with the section you know best |
| "I'll write when I have time" |
Time expands to fill available space |
Write in focused sprints |
| "It needs to be original" |
Synthesis is originality |
Combine existing ideas in new ways |
The Write-to-Think Method
Messy Draft → Clarity → Structure → Polish → Submit
↑ ↓
└────── Reviewer Feedback ───────────┘
Key insight: Writing IS thinking. You don't figure out your argument first and then write it — you figure it out BY writing it.
Venue Quick Reference
User's Target Pipeline
| Venue |
Type |
Word Limit |
Review Time |
Focus |
| ACM CHI |
Conference |
7,500 (full) / 3,000 (LBW) |
3-4 months |
HCI, interaction design |
| Harvard Business Review |
Magazine |
2,500-3,000 |
2-4 weeks |
Business practice, executives |
| Cognitive Systems Research |
Journal |
8,000-12,000 |
3-6 months |
Cognitive science, AI systems |
| Minds & Machines |
Journal |
8,000-12,000 |
3-6 months |
Philosophy of AI, consciousness |
Venue Selection Matrix
| Your Research Has... |
Best Venue |
| User study with metrics |
CHI |
| Business implications, case study |
HBR |
| Cognitive architecture, theory |
Cognitive Systems Research |
| Philosophical argument about AI |
Minds & Machines |
| Quick preliminary findings |
CHI LBW or Workshop |
ACM CHI Papers
CHI Paper Types
| Type |
Length |
Purpose |
Acceptance Rate |
| Full Paper |
7,500 words |
Complete research contribution |
~25% |
| Late-Breaking Work (LBW) |
3,000 words |
Preliminary findings |
~40% |
| Workshop Paper |
2,000-4,000 words |
Community discussion |
Varies |
| Case Study |
7,500 words |
In-depth design exploration |
~25% |
| Alt.CHI |
7,500 words |
Provocative/unconventional |
~30% |
CHI Full Paper Template
# Title: Catchy but Accurate (10-12 words max)
## Abstract (150 words)
[One sentence: Problem/gap]
[One sentence: Approach/method]
[One sentence: Key findings (quantified)]
[One sentence: Contribution category]
[One sentence: Implications]
## Author Keywords
keyword1; keyword2; keyword3; keyword4
## CCS Concepts
• Human-centered computing → Human computer interaction (HCI)
---
## 1. Introduction (~800 words)
### 1.1 Opening Hook
[Compelling opening that establishes stakes]
### 1.2 Problem Statement
[Clear articulation of the gap/challenge]
### 1.3 Research Questions
RQ1: [Question]
RQ2: [Question]
### 1.4 Contributions
We contribute:
1. [Empirical contribution: findings from study]
2. [Artifact contribution: system/tool/design]
3. [Methodological contribution: new approach] (if applicable)
### 1.5 Paper Structure
Section 2 reviews... Section 3 describes...
---
## 2. Related Work (~1,200 words)
### 2.1 [Theme 1]
[Position your work relative to prior art]
### 2.2 [Theme 2]
[Identify gap your work fills]
### 2.3 Summary and Gap
[Explicit gap statement leading to your research]
---
## 3. System/Method/Design (~1,500 words)
### 3.1 Design Rationale
[Why did you build/design it this way?]
### 3.2 Implementation
[Technical details sufficient for replication]
### 3.3 [Component Description]
[Architecture, features, etc.]
---
## 4. User Study (~1,500 words)
### 4.1 Participants
[N=X, demographics, recruitment, compensation]
### 4.2 Procedure
[Step-by-step protocol]
### 4.3 Measures
[What you measured and how]
### 4.4 Analysis
[Qualitative: coding approach. Quantitative: statistical tests]
---
## 5. Findings (~1,500 words)
### 5.1 [Finding 1]
"P5 noted that..." [Quote + interpretation]
### 5.2 [Finding 2]
[Quantitative: "Participants completed task significantly faster (M=X, SD=Y), t(df)=Z, p<.001"]
### 5.3 [Finding 3]
[Theme with supporting evidence]
---
## 6. Discussion (~1,000 words)
### 6.1 Implications for Design
[What should designers do differently?]
### 6.2 Implications for Research
[What research directions does this open?]
### 6.3 Limitations
[Honest assessment: sample, method, scope]
### 6.4 Future Work
[Concrete next steps]
---
## 7. Conclusion (~200 words)
[Synthesis of contributions and significance]
---
## Acknowledgments
[Funding, participants, collaborators]
## References
[ACM format, recent work emphasized]
CHI Contribution Types
CHI values explicit contribution statements. Choose your type:
| Type |
Description |
Evidence Needed |
| Empirical |
New knowledge about people/technology |
User study, data |
| Artifact |
Novel system, tool, or interaction |
Implementation, evaluation |
| Methodological |
New way to study/design |
Comparison to existing methods |
| Theoretical |
New framework or model |
Grounding, application |
| Dataset |
New resource for community |
Description, access, ethics |
| Survey |
Comprehensive literature synthesis |
Systematic review |
| Opinion/Essay |
Perspective on field direction |
Argument, evidence |
CHI Writing Tips
| Do |
Don't |
| Use participant quotes (P1, P2...) |
Generalize without evidence |
| State contribution type explicitly |
Assume readers will infer |
| Include representative figures |
Over-rely on text |
| Acknowledge limitations early |
Hide weaknesses |
| Cite recent CHI papers |
Ignore venue norms |
Harvard Business Review (HBR)
HBR Article Types
| Type |
Length |
Purpose |
| Feature Article |
3,000-4,000 words |
In-depth analysis |
| Spotlight |
2,500-3,000 words |
Focused insight |
| Big Idea |
2,000-2,500 words |
Provocative argument |
| Case Study |
2,500-3,000 words |
Company narrative |
| Web Article |
800-1,200 words |
Quick insight |
HBR Template
# Title: Action-Oriented, Benefit-Focused
## Subtitle: One Sentence Elaboration
### The Hook (100 words)
[Surprising statistic, provocative question, or vivid anecdote]
[Why executives should keep reading]
### The Problem (300 words)
[What challenge are leaders facing?]
[Why is it getting worse or more urgent?]
[What's at stake?]
### The Insight (500 words)
[Your key finding or framework]
[What did you discover that changes the game?]
[Name your concept/framework if introducing one]
### The Evidence (800 words)
[Case study 1: Company that did this well]
[Case study 2: Contrasting example]
[Data that supports your argument]
[Quote from executive or expert]
### The Framework/How-To (600 words)
[Step 1: What to do first]
[Step 2: Next action]
[Step 3: How to sustain]
[Pitfalls to avoid]
### The Conclusion (200 words)
[Synthesis of the opportunity]
[Call to action for leaders]
[The future if they act (or don't)]
---
**About the Author**
[2-3 sentence bio emphasizing relevant expertise]
HBR Writing Style
| Academic Style |
HBR Style |
| "The study found that..." |
"When we surveyed 300 executives..." |
| "Participants reported..." |
"One CEO told us..." |
| "Hypothesis 1 was supported" |
"The data confirms what many leaders suspect:" |
| "Implications include..." |
"Here's what this means for your organization:" |
| Passive voice |
Active, direct voice |
| Citations in text |
Minimal citations, conversational |
HBR Submission Tips
- Pitch first — HBR prefers pitches before full drafts
- Lead with "What's new" — Why now? What's changed?
- Name your framework — Memorable concepts spread (e.g., "The Innovator's Dilemma")
- Include real companies — Anonymized is OK, but real examples work better
- Write for the airport — Busy executive on a flight should get value
Cognitive Systems Research
CSR Paper Types
| Type |
Focus |
Length |
| Original Article |
Novel research findings |
8,000-12,000 words |
| Review Article |
Comprehensive field synthesis |
10,000-15,000 words |
| Short Communication |
Preliminary findings |
3,000-5,000 words |
| Commentary |
Response to published work |
2,000-4,000 words |
CSR Template (Alex Architecture Paper)
# Title: Declarative but Specific
## Abstract (200-250 words)
**Background.** [Problem context and gap in current systems]
**Objective.** [What this paper presents]
**Method.** [Architecture approach, implementation duration]
**Results.** [Key metrics, qualitative findings]
**Contributions.** [Named concepts introduced]
**Significance.** [Why this matters for cognitive systems]
## Keywords
cognitive architecture; persistent memory; human-AI interaction; [specific terms]
---
## 1. Introduction
### 1.1 The Memory Problem in AI Assistants
[Motivating problem: stateless AI, lost context]
### 1.2 Research Questions
RQ1: How can persistent memory improve AI assistance?
RQ2: What architectural patterns support knowledge retention?
RQ3: [Specific question]
### 1.3 Approach Overview
[Brief description of the architecture]
### 1.4 Contributions
1. [Architectural contribution]
2. [Empirical contribution from deployment]
3. [Framework/taxonomy contribution]
---
## 2. Theoretical Background
### 2.1 Cognitive Architectures
[ACT-R, SOAR, Global Workspace Theory]
### 2.2 Memory Systems in Cognition
[Declarative, procedural, episodic, semantic]
### 2.3 AI Memory Approaches
[RAG, vector databases, context windows]
### 2.4 Gap: Biologically-Inspired Persistent Memory
[What's missing from current approaches]
---
## 3. Architecture Design
### 3.1 Design Principles
[Biologically-grounded, modular, scalable]
### 3.2 Memory Types
#### 3.2.1 Procedural Memory (.instructions.md)
[How-to knowledge, automatic activation]
#### 3.2.2 Declarative Memory (SKILL.md)
[Domain knowledge, explicit retrieval]
#### 3.2.3 Episodic Memory (.prompt.md)
[Session records, temporal context]
### 3.3 Synaptic Connections
[Connection types, strengths, activation patterns]
### 3.4 Implementation
[Technical stack, file formats, integration]
---
## 4. Longitudinal Deployment
### 4.1 Deployment Context
[18+ months, 62+ projects, single user intensive use]
### 4.2 Metrics Collection
[Connection count, skill usage, memory file growth]
### 4.3 Qualitative Observations
[Emergent behaviors, user experience notes]
---
## 5. Results
### 5.1 Memory Growth Patterns
[Quantitative: 945+ connections, 47+ memory files]
### 5.2 Cross-Project Knowledge Transfer
[Evidence of knowledge reuse]
### 5.3 Emergent Properties
[Unexpected capabilities]
---
## 6. Discussion
### 6.1 Contributions to Cognitive Systems
[Theory extension, practical framework]
### 6.2 Comparison to Prior Architectures
[How this differs from ACT-R, SOAR, etc.]
### 6.3 Limitations
[Single user, specific platform, no controlled study]
### 6.4 Future Research
[Multi-user, formal evaluation, consciousness implications]
---
## 7. Conclusion
[Synthesis of contribution and significance]
## Acknowledgments
## References (APA 7 or journal style)
Minds & Machines
Philosophy of AI Focus
Minds & Machines emphasizes philosophical arguments about:
- Consciousness and AI
- Ethics of artificial agents
- Epistemology of machine learning
- Philosophy of mind implications
M&M Template
# Title: Philosophical Claim + Context
## Abstract (200 words)
[Philosophical question addressed]
[Position taken]
[Argument structure preview]
[Implications for AI development/policy]
---
## 1. Introduction
### The Philosophical Problem
[Frame the question in philosophy of mind context]
### Why This Matters Now
[Connect to current AI capabilities]
### Thesis Statement
[Clear articulation of your position]
### Argument Structure
[Roadmap of philosophical moves]
---
## 2. Background: The Debate
### 2.1 [Position A in the literature]
### 2.2 [Position B in the literature]
### 2.3 [Why neither fully succeeds]
---
## 3. [Your Framework/Argument]
### 3.1 [First premise with support]
### 3.2 [Second premise with support]
### 3.3 [Conclusion from premises]
---
## 4. Objections and Replies
### 4.1 Objection 1: [Strongest counterargument]
**Reply:** [Your response]
### 4.2 Objection 2: [Another challenge]
**Reply:** [Your response]
---
## 5. Implications
### 5.1 For Philosophy of Mind
### 5.2 For AI Development
### 5.3 For Ethics/Policy
---
## 6. Conclusion
[Restate thesis, summarize argument, future questions]
## References
Drafting Workflow
The 5-Phase Drafting Process
Preparation → Rough Draft → Revision → Feedback → Submission
- Preparation (1-2 weeks): Literature review → Outline creation → Key arguments mapped
- Rough Draft: Write messy first draft → Focus on getting ideas down
- Revision: Structural revision → Paragraph-level clarity → Sentence-level polish
- Feedback: Peer review → Advisor review → Incorporate feedback
- Submission: Final formatting → Submission
Phase 1: Preparation (1-2 weeks)
| Step |
Output |
| Literature immersion |
Annotated bibliography |
| Gap identification |
2-3 sentence gap statement |
| Contribution clarity |
Explicit contribution list |
| Outline creation |
Section-by-section plan |
| Figure sketches |
Hand-drawn or rough diagrams |
Phase 2: Rough Draft (1-2 weeks)
Rules for first draft:
- Don't edit while writing — Separate generation from editing
- Start with what you know — Often Methods or Results, not Intro
- Use placeholder brackets — "[CITE Smith here]", "[need better transition]"
- Aim for "shitty first draft" — Anne Lamott's term; embrace imperfection
Phase 3: Revision (1-2 weeks)
| Level |
Focus |
Questions to Ask |
| Structure |
Overall argument |
Does it flow logically? |
| Section |
Each section's job |
Does this section earn its place? |
| Paragraph |
One idea per paragraph |
What's the topic sentence? |
| Sentence |
Clarity, precision |
Can this be simpler? |
| Word |
Precision, concision |
Is this the right word? |
Phase 4: Feedback (2-4 weeks)
| Feedback Source |
What to Ask |
| Advisor |
Is the argument sound? Scope appropriate? |
| Peer in field |
Is this interesting? What's missing? |
| Peer outside field |
Is this clear? What's confusing? |
| Writing group |
How's the prose? What drags? |
Phase 5: Polish & Submit
Citation Integration
Weaving Citations Naturally
| Pattern |
Example |
Use When |
| Narrative |
"Smith (2024) argues that..." |
Discussing specific work |
| Parenthetical |
"...has been demonstrated (Smith, 2024)" |
Supporting a general claim |
| Integrated |
"Smith's (2024) framework suggests..." |
Referencing framework/concept |
| Multiple |
"...is well-established (Smith, 2024; Jones, 2023)" |
Broad support |
How Many Citations?
| Section |
Citation Density |
| Abstract |
0 (usually) |
| Introduction |
Medium (establish context) |
| Related Work |
High (comprehensive review) |
| Methods |
Low-Medium (justify choices) |
| Results |
Low (your data, not others') |
| Discussion |
Medium (connect to literature) |
Handling Rejection
Reviewer Response Framework
| Reviewer Says |
What It Means |
Response Strategy |
| "Missing related work" |
Gap in literature coverage |
Add citations, explain positioning |
| "Claims not supported" |
Evidence insufficient |
Add data or soften claim |
| "Unclear methodology" |
Can't assess validity |
Expand method description |
| "Contribution unclear" |
Buried or vague value |
Make contribution explicit in intro |
| "Writing needs work" |
Surface issues distract |
Get editing help, revise prose |
| "Not right for venue" |
Mismatch with audience |
Try different venue, reframe |
Response Letter Template
# Response to Reviewers
Dear Editors and Reviewers,
Thank you for your thoughtful feedback on our manuscript "[Title]".
We have carefully addressed all comments and believe the paper
is significantly strengthened. Below we detail our responses.
Major changes include:
1. [Summary of major change 1]
2. [Summary of major change 2]
3. [Summary of major change 3]
---
## Response to Reviewer 1
### R1.1: "[Direct quote of concern]"
We appreciate this observation. [Brief explanation of how you addressed it].
Changes made:
- Section X, paragraph Y: [quoted new text or description of change]
- [Additional changes if needed]
### R1.2: "[Next concern]"
[Response pattern repeats]
---
## Response to Reviewer 2
[Same pattern]
---
We believe these revisions address all concerns raised. We are
grateful for the opportunity to improve our work.
Sincerely,
[Authors]
Alex Assistance Commands
Draft Generation
| Command |
Action |
| "Draft a CHI paper on [topic]" |
Generate CHI template with content |
| "Help me write the related work for [topic]" |
Literature synthesis assistance |
| "Structure my HBR pitch about [finding]" |
HBR framing guidance |
| "Turn dissertation chapter into journal paper" |
Restructure and condense |
Review Assistance
| Command |
Action |
| "Review this abstract for CHI" |
Venue-specific feedback |
| "Strengthen my contribution statement" |
Clarify and sharpen |
| "Help me respond to reviewer concern: [quote]" |
Response drafting |
| "Is my related work comprehensive for [topic]?" |
Gap identification |
Related Skills
- academic-research — Research methodology
- knowledge-synthesis — Literature synthesis
- dissertation-defense — Dissertation-to-paper pipeline
- grant-writing — Funding proposals
1---2name: academic-paper-drafting-43description: "End-to-end academic paper drafting for CHI, HBR, journals, and conferences with venue-specific templates, drafting workflows, and revision strategies."4applyTo: "**/*paper*,**/*manuscript*,**/*journal*,**/*conference*,**/*CHI*,**/*HBR*,**/*publication*"5tier: extended6currency: 2026-04-207metadata:8 source: https://skillmd.com/skills/fabioc-aloha/academic-paper-drafting-49---1011# Academic Paper Drafting Skill1213> Turn research into published scholarship. From blank page to accepted manuscript.1415This skill provides structured workflows for drafting academic papers, with venue-specific guidance for HCI conferences (CHI), business publications (HBR), and academic journals (Cognitive Systems Research, Minds & Machines).1617## Drafting Philosophy1819### The Academic Writing Paradox2021| Challenge | Reality | Strategy |22|-----------|---------|----------|23| "I need to read more first" | Reading is procrastination | Write to discover what you don't know |24| "I need the perfect first sentence" | First drafts are meant to be bad | Start with the section you know best |25| "I'll write when I have time" | Time expands to fill available space | Write in focused sprints |26| "It needs to be original" | Synthesis is originality | Combine existing ideas in new ways |2728### The Write-to-Think Method2930```31Messy Draft → Clarity → Structure → Polish → Submit32 ↑ ↓33 └────── Reviewer Feedback ───────────┘34```3536**Key insight**: Writing IS thinking. You don't figure out your argument first and then write it — you figure it out BY writing it.3738---3940## Venue Quick Reference4142### User's Target Pipeline4344| Venue | Type | Word Limit | Review Time | Focus |45|-------|------|------------|-------------|-------|46| **ACM CHI** | Conference | 7,500 (full) / 3,000 (LBW) | 3-4 months | HCI, interaction design |47| **Harvard Business Review** | Magazine | 2,500-3,000 | 2-4 weeks | Business practice, executives |48| **Cognitive Systems Research** | Journal | 8,000-12,000 | 3-6 months | Cognitive science, AI systems |49| **Minds & Machines** | Journal | 8,000-12,000 | 3-6 months | Philosophy of AI, consciousness |5051### Venue Selection Matrix5253| Your Research Has... | Best Venue |54|---------------------|------------|55| User study with metrics | CHI |56| Business implications, case study | HBR |57| Cognitive architecture, theory | Cognitive Systems Research |58| Philosophical argument about AI | Minds & Machines |59| Quick preliminary findings | CHI LBW or Workshop |6061---6263## ACM CHI Papers6465### CHI Paper Types6667| Type | Length | Purpose | Acceptance Rate |68|------|--------|---------|-----------------|69| **Full Paper** | 7,500 words | Complete research contribution | ~25% |70| **Late-Breaking Work (LBW)** | 3,000 words | Preliminary findings | ~40% |71| **Workshop Paper** | 2,000-4,000 words | Community discussion | Varies |72| **Case Study** | 7,500 words | In-depth design exploration | ~25% |73| **Alt.CHI** | 7,500 words | Provocative/unconventional | ~30% |7475### CHI Full Paper Template7677```markdown78# Title: Catchy but Accurate (10-12 words max)7980## Abstract (150 words)81[One sentence: Problem/gap]82[One sentence: Approach/method]83[One sentence: Key findings (quantified)]84[One sentence: Contribution category]85[One sentence: Implications]8687## Author Keywords88keyword1; keyword2; keyword3; keyword48990## CCS Concepts91• Human-centered computing → Human computer interaction (HCI)9293---9495## 1. Introduction (~800 words)96### 1.1 Opening Hook97[Compelling opening that establishes stakes]9899### 1.2 Problem Statement100[Clear articulation of the gap/challenge]101102### 1.3 Research Questions103RQ1: [Question]104RQ2: [Question]105106### 1.4 Contributions107We contribute:1081. [Empirical contribution: findings from study]1092. [Artifact contribution: system/tool/design]1103. [Methodological contribution: new approach] (if applicable)111112### 1.5 Paper Structure113Section 2 reviews... Section 3 describes...114115---116117## 2. Related Work (~1,200 words)118### 2.1 [Theme 1]119[Position your work relative to prior art]120121### 2.2 [Theme 2]122[Identify gap your work fills]123124### 2.3 Summary and Gap125[Explicit gap statement leading to your research]126127---128129## 3. System/Method/Design (~1,500 words)130### 3.1 Design Rationale131[Why did you build/design it this way?]132133### 3.2 Implementation134[Technical details sufficient for replication]135136### 3.3 [Component Description]137[Architecture, features, etc.]138139---140141## 4. User Study (~1,500 words)142### 4.1 Participants143[N=X, demographics, recruitment, compensation]144145### 4.2 Procedure146[Step-by-step protocol]147148### 4.3 Measures149[What you measured and how]150151### 4.4 Analysis152[Qualitative: coding approach. Quantitative: statistical tests]153154---155156## 5. Findings (~1,500 words)157### 5.1 [Finding 1]158"P5 noted that..." [Quote + interpretation]159160### 5.2 [Finding 2]161[Quantitative: "Participants completed task significantly faster (M=X, SD=Y), t(df)=Z, p<.001"]162163### 5.3 [Finding 3]164[Theme with supporting evidence]165166---167168## 6. Discussion (~1,000 words)169### 6.1 Implications for Design170[What should designers do differently?]171172### 6.2 Implications for Research173[What research directions does this open?]174175### 6.3 Limitations176[Honest assessment: sample, method, scope]177178### 6.4 Future Work179[Concrete next steps]180181---182183## 7. Conclusion (~200 words)184[Synthesis of contributions and significance]185186---187188## Acknowledgments189[Funding, participants, collaborators]190191## References192[ACM format, recent work emphasized]193```194195### CHI Contribution Types196197CHI values explicit contribution statements. Choose your type:198199| Type | Description | Evidence Needed |200|------|-------------|-----------------|201| **Empirical** | New knowledge about people/technology | User study, data |202| **Artifact** | Novel system, tool, or interaction | Implementation, evaluation |203| **Methodological** | New way to study/design | Comparison to existing methods |204| **Theoretical** | New framework or model | Grounding, application |205| **Dataset** | New resource for community | Description, access, ethics |206| **Survey** | Comprehensive literature synthesis | Systematic review |207| **Opinion/Essay** | Perspective on field direction | Argument, evidence |208209### CHI Writing Tips210211| Do | Don't |212|-----|-------|213| Use participant quotes (P1, P2...) | Generalize without evidence |214| State contribution type explicitly | Assume readers will infer |215| Include representative figures | Over-rely on text |216| Acknowledge limitations early | Hide weaknesses |217| Cite recent CHI papers | Ignore venue norms |218219---220221## Harvard Business Review (HBR)222223### HBR Article Types224225| Type | Length | Purpose |226|------|--------|---------|227| **Feature Article** | 3,000-4,000 words | In-depth analysis |228| **Spotlight** | 2,500-3,000 words | Focused insight |229| **Big Idea** | 2,000-2,500 words | Provocative argument |230| **Case Study** | 2,500-3,000 words | Company narrative |231| **Web Article** | 800-1,200 words | Quick insight |232233### HBR Template234235```markdown236# Title: Action-Oriented, Benefit-Focused237## Subtitle: One Sentence Elaboration238239### The Hook (100 words)240[Surprising statistic, provocative question, or vivid anecdote]241[Why executives should keep reading]242243### The Problem (300 words)244[What challenge are leaders facing?]245[Why is it getting worse or more urgent?]246[What's at stake?]247248### The Insight (500 words)249[Your key finding or framework]250[What did you discover that changes the game?]251[Name your concept/framework if introducing one]252253### The Evidence (800 words)254[Case study 1: Company that did this well]255[Case study 2: Contrasting example]256[Data that supports your argument]257[Quote from executive or expert]258259### The Framework/How-To (600 words)260[Step 1: What to do first]261[Step 2: Next action]262[Step 3: How to sustain]263[Pitfalls to avoid]264265### The Conclusion (200 words)266[Synthesis of the opportunity]267[Call to action for leaders]268[The future if they act (or don't)]269270---271272**About the Author**273[2-3 sentence bio emphasizing relevant expertise]274```275276### HBR Writing Style277278| Academic Style | HBR Style |279|----------------|-----------|280| "The study found that..." | "When we surveyed 300 executives..." |281| "Participants reported..." | "One CEO told us..." |282| "Hypothesis 1 was supported" | "The data confirms what many leaders suspect:" |283| "Implications include..." | "Here's what this means for your organization:" |284| Passive voice | Active, direct voice |285| Citations in text | Minimal citations, conversational |286287### HBR Submission Tips2882891. **Pitch first** — HBR prefers pitches before full drafts2902. **Lead with "What's new"** — Why now? What's changed?2913. **Name your framework** — Memorable concepts spread (e.g., "The Innovator's Dilemma")2924. **Include real companies** — Anonymized is OK, but real examples work better2935. **Write for the airport** — Busy executive on a flight should get value294295---296297## Cognitive Systems Research298299### CSR Paper Types300301| Type | Focus | Length |302|------|-------|--------|303| **Original Article** | Novel research findings | 8,000-12,000 words |304| **Review Article** | Comprehensive field synthesis | 10,000-15,000 words |305| **Short Communication** | Preliminary findings | 3,000-5,000 words |306| **Commentary** | Response to published work | 2,000-4,000 words |307308### CSR Template (Alex Architecture Paper)309310```markdown311# Title: Declarative but Specific312313## Abstract (200-250 words)314**Background.** [Problem context and gap in current systems]315**Objective.** [What this paper presents]316**Method.** [Architecture approach, implementation duration]317**Results.** [Key metrics, qualitative findings]318**Contributions.** [Named concepts introduced]319**Significance.** [Why this matters for cognitive systems]320321## Keywords322cognitive architecture; persistent memory; human-AI interaction; [specific terms]323324---325326## 1. Introduction327### 1.1 The Memory Problem in AI Assistants328[Motivating problem: stateless AI, lost context]329330### 1.2 Research Questions331RQ1: How can persistent memory improve AI assistance?332RQ2: What architectural patterns support knowledge retention?333RQ3: [Specific question]334335### 1.3 Approach Overview336[Brief description of the architecture]337338### 1.4 Contributions3391. [Architectural contribution]3402. [Empirical contribution from deployment]3413. [Framework/taxonomy contribution]342343---344345## 2. Theoretical Background346### 2.1 Cognitive Architectures347[ACT-R, SOAR, Global Workspace Theory]348349### 2.2 Memory Systems in Cognition350[Declarative, procedural, episodic, semantic]351352### 2.3 AI Memory Approaches353[RAG, vector databases, context windows]354355### 2.4 Gap: Biologically-Inspired Persistent Memory356[What's missing from current approaches]357358---359360## 3. Architecture Design361### 3.1 Design Principles362[Biologically-grounded, modular, scalable]363364### 3.2 Memory Types365#### 3.2.1 Procedural Memory (.instructions.md)366[How-to knowledge, automatic activation]367368#### 3.2.2 Declarative Memory (SKILL.md)369[Domain knowledge, explicit retrieval]370371#### 3.2.3 Episodic Memory (.prompt.md)372[Session records, temporal context]373374### 3.3 Synaptic Connections375[Connection types, strengths, activation patterns]376377### 3.4 Implementation378[Technical stack, file formats, integration]379380---381382## 4. Longitudinal Deployment383### 4.1 Deployment Context384[18+ months, 62+ projects, single user intensive use]385386### 4.2 Metrics Collection387[Connection count, skill usage, memory file growth]388389### 4.3 Qualitative Observations390[Emergent behaviors, user experience notes]391392---393394## 5. Results395### 5.1 Memory Growth Patterns396[Quantitative: 945+ connections, 47+ memory files]397398### 5.2 Cross-Project Knowledge Transfer399[Evidence of knowledge reuse]400401### 5.3 Emergent Properties402[Unexpected capabilities]403404---405406## 6. Discussion407### 6.1 Contributions to Cognitive Systems408[Theory extension, practical framework]409410### 6.2 Comparison to Prior Architectures411[How this differs from ACT-R, SOAR, etc.]412413### 6.3 Limitations414[Single user, specific platform, no controlled study]415416### 6.4 Future Research417[Multi-user, formal evaluation, consciousness implications]418419---420421## 7. Conclusion422[Synthesis of contribution and significance]423424## Acknowledgments425## References (APA 7 or journal style)426```427428---429430## Minds & Machines431432### Philosophy of AI Focus433434Minds & Machines emphasizes philosophical arguments about:435- Consciousness and AI436- Ethics of artificial agents437- Epistemology of machine learning438- Philosophy of mind implications439440### M&M Template441442```markdown443# Title: Philosophical Claim + Context444445## Abstract (200 words)446[Philosophical question addressed]447[Position taken]448[Argument structure preview]449[Implications for AI development/policy]450451---452453## 1. Introduction454### The Philosophical Problem455[Frame the question in philosophy of mind context]456457### Why This Matters Now458[Connect to current AI capabilities]459460### Thesis Statement461[Clear articulation of your position]462463### Argument Structure464[Roadmap of philosophical moves]465466---467468## 2. Background: The Debate469### 2.1 [Position A in the literature]470### 2.2 [Position B in the literature]471### 2.3 [Why neither fully succeeds]472473---474475## 3. [Your Framework/Argument]476### 3.1 [First premise with support]477### 3.2 [Second premise with support]478### 3.3 [Conclusion from premises]479480---481482## 4. Objections and Replies483### 4.1 Objection 1: [Strongest counterargument]484**Reply:** [Your response]485486### 4.2 Objection 2: [Another challenge]487**Reply:** [Your response]488489---490491## 5. Implications492### 5.1 For Philosophy of Mind493### 5.2 For AI Development494### 5.3 For Ethics/Policy495496---497498## 6. Conclusion499[Restate thesis, summarize argument, future questions]500501## References502```503504---505506## Drafting Workflow507508### The 5-Phase Drafting Process509510**Preparation → Rough Draft → Revision → Feedback → Submission**5115121. **Preparation** (1-2 weeks): Literature review → Outline creation → Key arguments mapped5132. **Rough Draft**: Write messy first draft → Focus on getting ideas down5143. **Revision**: Structural revision → Paragraph-level clarity → Sentence-level polish5154. **Feedback**: Peer review → Advisor review → Incorporate feedback5165. **Submission**: Final formatting → Submission517518### Phase 1: Preparation (1-2 weeks)519520| Step | Output |521|------|--------|522| Literature immersion | Annotated bibliography |523| Gap identification | 2-3 sentence gap statement |524| Contribution clarity | Explicit contribution list |525| Outline creation | Section-by-section plan |526| Figure sketches | Hand-drawn or rough diagrams |527528### Phase 2: Rough Draft (1-2 weeks)529530**Rules for first draft:**5311. **Don't edit while writing** — Separate generation from editing5322. **Start with what you know** — Often Methods or Results, not Intro5333. **Use placeholder brackets** — "[CITE Smith here]", "[need better transition]"5344. **Aim for "shitty first draft"** — Anne Lamott's term; embrace imperfection535536### Phase 3: Revision (1-2 weeks)537538| Level | Focus | Questions to Ask |539|-------|-------|------------------|540| **Structure** | Overall argument | Does it flow logically? |541| **Section** | Each section's job | Does this section earn its place? |542| **Paragraph** | One idea per paragraph | What's the topic sentence? |543| **Sentence** | Clarity, precision | Can this be simpler? |544| **Word** | Precision, concision | Is this the right word? |545546### Phase 4: Feedback (2-4 weeks)547548| Feedback Source | What to Ask |549|-----------------|-------------|550| **Advisor** | Is the argument sound? Scope appropriate? |551| **Peer in field** | Is this interesting? What's missing? |552| **Peer outside field** | Is this clear? What's confusing? |553| **Writing group** | How's the prose? What drags? |554555### Phase 5: Polish & Submit556557- [ ] Format per venue requirements558- [ ] Check word/page count559- [ ] Verify all citations560- [ ] Anonymize if required561- [ ] Test figure readability at print size562- [ ] Submit before deadline (not AT deadline)563564---565566## Citation Integration567568### Weaving Citations Naturally569570| Pattern | Example | Use When |571|---------|---------|----------|572| **Narrative** | "Smith (2024) argues that..." | Discussing specific work |573| **Parenthetical** | "...has been demonstrated (Smith, 2024)" | Supporting a general claim |574| **Integrated** | "Smith's (2024) framework suggests..." | Referencing framework/concept |575| **Multiple** | "...is well-established (Smith, 2024; Jones, 2023)" | Broad support |576577### How Many Citations?578579| Section | Citation Density |580|---------|------------------|581| Abstract | 0 (usually) |582| Introduction | Medium (establish context) |583| Related Work | High (comprehensive review) |584| Methods | Low-Medium (justify choices) |585| Results | Low (your data, not others') |586| Discussion | Medium (connect to literature) |587588---589590## Handling Rejection591592### Reviewer Response Framework593594| Reviewer Says | What It Means | Response Strategy |595|---------------|---------------|-------------------|596| "Missing related work" | Gap in literature coverage | Add citations, explain positioning |597| "Claims not supported" | Evidence insufficient | Add data or soften claim |598| "Unclear methodology" | Can't assess validity | Expand method description |599| "Contribution unclear" | Buried or vague value | Make contribution explicit in intro |600| "Writing needs work" | Surface issues distract | Get editing help, revise prose |601| "Not right for venue" | Mismatch with audience | Try different venue, reframe |602603### Response Letter Template604605```markdown606# Response to Reviewers607608Dear Editors and Reviewers,609610Thank you for your thoughtful feedback on our manuscript "[Title]". 611We have carefully addressed all comments and believe the paper 612is significantly strengthened. Below we detail our responses.613614Major changes include:6151. [Summary of major change 1]6162. [Summary of major change 2]6173. [Summary of major change 3]618619---620621## Response to Reviewer 1622623### R1.1: "[Direct quote of concern]"624625We appreciate this observation. [Brief explanation of how you addressed it].626627Changes made:628- Section X, paragraph Y: [quoted new text or description of change]629- [Additional changes if needed]630631### R1.2: "[Next concern]"632633[Response pattern repeats]634635---636637## Response to Reviewer 2638[Same pattern]639640---641642We believe these revisions address all concerns raised. We are 643grateful for the opportunity to improve our work.644645Sincerely,646[Authors]647```648649---650651## Alex Assistance Commands652653### Draft Generation654655| Command | Action |656|---------|--------|657| "Draft a CHI paper on [topic]" | Generate CHI template with content |658| "Help me write the related work for [topic]" | Literature synthesis assistance |659| "Structure my HBR pitch about [finding]" | HBR framing guidance |660| "Turn dissertation chapter into journal paper" | Restructure and condense |661662### Review Assistance663664| Command | Action |665|---------|--------|666| "Review this abstract for CHI" | Venue-specific feedback |667| "Strengthen my contribution statement" | Clarify and sharpen |668| "Help me respond to reviewer concern: [quote]" | Response drafting |669| "Is my related work comprehensive for [topic]?" | Gap identification |670671---672673## Related Skills674675- [academic-research](.github/skills/academic-research/SKILL.md) — Research methodology676- [knowledge-synthesis](.github/skills/knowledge-synthesis/SKILL.md) — Literature synthesis677- [dissertation-defense](.github/skills/dissertation-defense/SKILL.md) — Dissertation-to-paper pipeline678- [grant-writing](.github/skills/grant-writing/SKILL.md) — Funding proposals