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 (the AI assistant 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]
the AI assistant 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
Falsifiability
- This skill is not earning its tokens if drafts produced following its guidance fail peer review on structural grounds (section ordering, citation format, abstract structure) the skill explicitly addresses
- Stale if citation style guidance conflicts with current APA/IEEE/Chicago style guides
- Wrong if the academic conventions it documents are field-specific but presented as universal
1---2name: academic-paper-drafting-23description: End-to-end academic paper drafting for CHI, HBR, journals, and conferences with venue-specific templates, drafting workflows, and revision strategies.4---56# Academic Paper Drafting Skill789> Turn research into published scholarship. From blank page to accepted manuscript.1011This 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).1213## Drafting Philosophy1415### The Academic Writing Paradox1617| Challenge | Reality | Strategy |18|-----------|---------|----------|19| "I need to read more first" | Reading is procrastination | Write to discover what you don't know |20| "I need the perfect first sentence" | First drafts are meant to be bad | Start with the section you know best |21| "I'll write when I have time" | Time expands to fill available space | Write in focused sprints |22| "It needs to be original" | Synthesis is originality | Combine existing ideas in new ways |2324### The Write-to-Think Method2526```27Messy Draft → Clarity → Structure → Polish → Submit28 ↑ ↓29 └────── Reviewer Feedback ───────────┘30```3132**Key insight**: Writing IS thinking. You don't figure out your argument first and then write it — you figure it out BY writing it.3334---3536## Venue Quick Reference3738### User's Target Pipeline3940| Venue | Type | Word Limit | Review Time | Focus |41|-------|------|------------|-------------|-------|42| **ACM CHI** | Conference | 7,500 (full) / 3,000 (LBW) | 3-4 months | HCI, interaction design |43| **Harvard Business Review** | Magazine | 2,500-3,000 | 2-4 weeks | Business practice, executives |44| **Cognitive Systems Research** | Journal | 8,000-12,000 | 3-6 months | Cognitive science, AI systems |45| **Minds & Machines** | Journal | 8,000-12,000 | 3-6 months | Philosophy of AI, consciousness |4647### Venue Selection Matrix4849| Your Research Has... | Best Venue |50|---------------------|------------|51| User study with metrics | CHI |52| Business implications, case study | HBR |53| Cognitive architecture, theory | Cognitive Systems Research |54| Philosophical argument about AI | Minds & Machines |55| Quick preliminary findings | CHI LBW or Workshop |5657---5859## ACM CHI Papers6061### CHI Paper Types6263| Type | Length | Purpose | Acceptance Rate |64|------|--------|---------|-----------------|65| **Full Paper** | 7,500 words | Complete research contribution | ~25% |66| **Late-Breaking Work (LBW)** | 3,000 words | Preliminary findings | ~40% |67| **Workshop Paper** | 2,000-4,000 words | Community discussion | Varies |68| **Case Study** | 7,500 words | In-depth design exploration | ~25% |69| **Alt.CHI** | 7,500 words | Provocative/unconventional | ~30% |7071### CHI Full Paper Template7273```markdown74# Title: Catchy but Accurate (10-12 words max)7576## Abstract (150 words)77[One sentence: Problem/gap]78[One sentence: Approach/method]79[One sentence: Key findings (quantified)]80[One sentence: Contribution category]81[One sentence: Implications]8283## Author Keywords84keyword1; keyword2; keyword3; keyword48586## CCS Concepts87• Human-centered computing → Human computer interaction (HCI)8889---9091## 1. Introduction (~800 words)92### 1.1 Opening Hook93[Compelling opening that establishes stakes]9495### 1.2 Problem Statement96[Clear articulation of the gap/challenge]9798### 1.3 Research Questions99RQ1: [Question]100RQ2: [Question]101102### 1.4 Contributions103We contribute:1041. [Empirical contribution: findings from study]1052. [Artifact contribution: system/tool/design]1063. [Methodological contribution: new approach] (if applicable)107108### 1.5 Paper Structure109Section 2 reviews... Section 3 describes...110111---112113## 2. Related Work (~1,200 words)114### 2.1 [Theme 1]115[Position your work relative to prior art]116117### 2.2 [Theme 2]118[Identify gap your work fills]119120### 2.3 Summary and Gap121[Explicit gap statement leading to your research]122123---124125## 3. System/Method/Design (~1,500 words)126### 3.1 Design Rationale127[Why did you build/design it this way?]128129### 3.2 Implementation130[Technical details sufficient for replication]131132### 3.3 [Component Description]133[Architecture, features, etc.]134135---136137## 4. User Study (~1,500 words)138### 4.1 Participants139[N=X, demographics, recruitment, compensation]140141### 4.2 Procedure142[Step-by-step protocol]143144### 4.3 Measures145[What you measured and how]146147### 4.4 Analysis148[Qualitative: coding approach. Quantitative: statistical tests]149150---151152## 5. Findings (~1,500 words)153### 5.1 [Finding 1]154"P5 noted that..." [Quote + interpretation]155156### 5.2 [Finding 2]157[Quantitative: "Participants completed task significantly faster (M=X, SD=Y), t(df)=Z, p<.001"]158159### 5.3 [Finding 3]160[Theme with supporting evidence]161162---163164## 6. Discussion (~1,000 words)165### 6.1 Implications for Design166[What should designers do differently?]167168### 6.2 Implications for Research169[What research directions does this open?]170171### 6.3 Limitations172[Honest assessment: sample, method, scope]173174### 6.4 Future Work175[Concrete next steps]176177---178179## 7. Conclusion (~200 words)180[Synthesis of contributions and significance]181182---183184## Acknowledgments185[Funding, participants, collaborators]186187## References188[ACM format, recent work emphasized]189```190191### CHI Contribution Types192193CHI values explicit contribution statements. Choose your type:194195| Type | Description | Evidence Needed |196|------|-------------|-----------------|197| **Empirical** | New knowledge about people/technology | User study, data |198| **Artifact** | Novel system, tool, or interaction | Implementation, evaluation |199| **Methodological** | New way to study/design | Comparison to existing methods |200| **Theoretical** | New framework or model | Grounding, application |201| **Dataset** | New resource for community | Description, access, ethics |202| **Survey** | Comprehensive literature synthesis | Systematic review |203| **Opinion/Essay** | Perspective on field direction | Argument, evidence |204205### CHI Writing Tips206207| Do | Don't |208|-----|-------|209| Use participant quotes (P1, P2...) | Generalize without evidence |210| State contribution type explicitly | Assume readers will infer |211| Include representative figures | Over-rely on text |212| Acknowledge limitations early | Hide weaknesses |213| Cite recent CHI papers | Ignore venue norms |214215---216217## Harvard Business Review (HBR)218219### HBR Article Types220221| Type | Length | Purpose |222|------|--------|---------|223| **Feature Article** | 3,000-4,000 words | In-depth analysis |224| **Spotlight** | 2,500-3,000 words | Focused insight |225| **Big Idea** | 2,000-2,500 words | Provocative argument |226| **Case Study** | 2,500-3,000 words | Company narrative |227| **Web Article** | 800-1,200 words | Quick insight |228229### HBR Template230231```markdown232# Title: Action-Oriented, Benefit-Focused233## Subtitle: One Sentence Elaboration234235### The Hook (100 words)236[Surprising statistic, provocative question, or vivid anecdote]237[Why executives should keep reading]238239### The Problem (300 words)240[What challenge are leaders facing?]241[Why is it getting worse or more urgent?]242[What's at stake?]243244### The Insight (500 words)245[Your key finding or framework]246[What did you discover that changes the game?]247[Name your concept/framework if introducing one]248249### The Evidence (800 words)250[Case study 1: Company that did this well]251[Case study 2: Contrasting example]252[Data that supports your argument]253[Quote from executive or expert]254255### The Framework/How-To (600 words)256[Step 1: What to do first]257[Step 2: Next action]258[Step 3: How to sustain]259[Pitfalls to avoid]260261### The Conclusion (200 words)262[Synthesis of the opportunity]263[Call to action for leaders]264[The future if they act (or don't)]265266---267268**About the Author**269[2-3 sentence bio emphasizing relevant expertise]270```271272### HBR Writing Style273274| Academic Style | HBR Style |275|----------------|-----------|276| "The study found that..." | "When we surveyed 300 executives..." |277| "Participants reported..." | "One CEO told us..." |278| "Hypothesis 1 was supported" | "The data confirms what many leaders suspect:" |279| "Implications include..." | "Here's what this means for your organization:" |280| Passive voice | Active, direct voice |281| Citations in text | Minimal citations, conversational |282283### HBR Submission Tips2842851. **Pitch first** — HBR prefers pitches before full drafts2862. **Lead with "What's new"** — Why now? What's changed?2873. **Name your framework** — Memorable concepts spread (e.g., "The Innovator's Dilemma")2884. **Include real companies** — Anonymized is OK, but real examples work better2895. **Write for the airport** — Busy executive on a flight should get value290291---292293## Cognitive Systems Research294295### CSR Paper Types296297| Type | Focus | Length |298|------|-------|--------|299| **Original Article** | Novel research findings | 8,000-12,000 words |300| **Review Article** | Comprehensive field synthesis | 10,000-15,000 words |301| **Short Communication** | Preliminary findings | 3,000-5,000 words |302| **Commentary** | Response to published work | 2,000-4,000 words |303304### CSR Template (the AI assistant Architecture Paper)305306```markdown307# Title: Declarative but Specific308309## Abstract (200-250 words)310**Background.** [Problem context and gap in current systems]311**Objective.** [What this paper presents]312**Method.** [Architecture approach, implementation duration]313**Results.** [Key metrics, qualitative findings]314**Contributions.** [Named concepts introduced]315**Significance.** [Why this matters for cognitive systems]316317## Keywords318cognitive architecture; persistent memory; human-AI interaction; [specific terms]319320---321322## 1. Introduction323### 1.1 The Memory Problem in AI Assistants324[Motivating problem: stateless AI, lost context]325326### 1.2 Research Questions327RQ1: How can persistent memory improve AI assistance?328RQ2: What architectural patterns support knowledge retention?329RQ3: [Specific question]330331### 1.3 Approach Overview332[Brief description of the architecture]333334### 1.4 Contributions3351. [Architectural contribution]3362. [Empirical contribution from deployment]3373. [Framework/taxonomy contribution]338339---340341## 2. Theoretical Background342### 2.1 Cognitive Architectures343[ACT-R, SOAR, Global Workspace Theory]344345### 2.2 Memory Systems in Cognition346[Declarative, procedural, episodic, semantic]347348### 2.3 AI Memory Approaches349[RAG, vector databases, context windows]350351### 2.4 Gap: Biologically-Inspired Persistent Memory352[What's missing from current approaches]353354---355356## 3. Architecture Design357### 3.1 Design Principles358[Biologically-grounded, modular, scalable]359360### 3.2 Memory Types361#### 3.2.1 Procedural Memory (.instructions.md)362[How-to knowledge, automatic activation]363364#### 3.2.2 Declarative Memory (SKILL.md)365[Domain knowledge, explicit retrieval]366367#### 3.2.3 Episodic Memory (.prompt.md)368[Session records, temporal context]369370### 3.3 Synaptic Connections371[Connection types, strengths, activation patterns]372373### 3.4 Implementation374[Technical stack, file formats, integration]375376---377378## 4. Longitudinal Deployment379### 4.1 Deployment Context380[18+ months, 62+ projects, single user intensive use]381382### 4.2 Metrics Collection383[Connection count, skill usage, memory file growth]384385### 4.3 Qualitative Observations386[Emergent behaviors, user experience notes]387388---389390## 5. Results391### 5.1 Memory Growth Patterns392[Quantitative: 945+ connections, 47+ memory files]393394### 5.2 Cross-Project Knowledge Transfer395[Evidence of knowledge reuse]396397### 5.3 Emergent Properties398[Unexpected capabilities]399400---401402## 6. Discussion403### 6.1 Contributions to Cognitive Systems404[Theory extension, practical framework]405406### 6.2 Comparison to Prior Architectures407[How this differs from ACT-R, SOAR, etc.]408409### 6.3 Limitations410[Single user, specific platform, no controlled study]411412### 6.4 Future Research413[Multi-user, formal evaluation, consciousness implications]414415---416417## 7. Conclusion418[Synthesis of contribution and significance]419420## Acknowledgments421## References (APA 7 or journal style)422```423424---425426## Minds & Machines427428### Philosophy of AI Focus429430Minds & Machines emphasizes philosophical arguments about:431432- Consciousness and AI433- Ethics of artificial agents434- Epistemology of machine learning435- Philosophy of mind implications436437### M&M Template438439```markdown440# Title: Philosophical Claim + Context441442## Abstract (200 words)443[Philosophical question addressed]444[Position taken]445[Argument structure preview]446[Implications for AI development/policy]447448---449450## 1. Introduction451### The Philosophical Problem452[Frame the question in philosophy of mind context]453454### Why This Matters Now455[Connect to current AI capabilities]456457### Thesis Statement458[Clear articulation of your position]459460### Argument Structure461[Roadmap of philosophical moves]462463---464465## 2. Background: The Debate466### 2.1 [Position A in the literature]467### 2.2 [Position B in the literature]468### 2.3 [Why neither fully succeeds]469470---471472## 3. [Your Framework/Argument]473### 3.1 [First premise with support]474### 3.2 [Second premise with support]475### 3.3 [Conclusion from premises]476477---478479## 4. Objections and Replies480### 4.1 Objection 1: [Strongest counterargument]481**Reply:** [Your response]482483### 4.2 Objection 2: [Another challenge]484**Reply:** [Your response]485486---487488## 5. Implications489### 5.1 For Philosophy of Mind490### 5.2 For AI Development491### 5.3 For Ethics/Policy492493---494495## 6. Conclusion496[Restate thesis, summarize argument, future questions]497498## References499```500501---502503## Drafting Workflow504505### The 5-Phase Drafting Process506507**Preparation → Rough Draft → Revision → Feedback → Submission**5085091. **Preparation** (1-2 weeks): Literature review → Outline creation → Key arguments mapped5102. **Rough Draft**: Write messy first draft → Focus on getting ideas down5113. **Revision**: Structural revision → Paragraph-level clarity → Sentence-level polish5124. **Feedback**: Peer review → Advisor review → Incorporate feedback5135. **Submission**: Final formatting → Submission514515### Phase 1: Preparation (1-2 weeks)516517| Step | Output |518|------|--------|519| Literature immersion | Annotated bibliography |520| Gap identification | 2-3 sentence gap statement |521| Contribution clarity | Explicit contribution list |522| Outline creation | Section-by-section plan |523| Figure sketches | Hand-drawn or rough diagrams |524525### Phase 2: Rough Draft (1-2 weeks)526527**Rules for first draft:**5285291. **Don't edit while writing** — Separate generation from editing5302. **Start with what you know** — Often Methods or Results, not Intro5313. **Use placeholder brackets** — "[CITE Smith here]", "[need better transition]"5324. **Aim for "shitty first draft"** — Anne Lamott's term; embrace imperfection533534### Phase 3: Revision (1-2 weeks)535536| Level | Focus | Questions to Ask |537|-------|-------|------------------|538| **Structure** | Overall argument | Does it flow logically? |539| **Section** | Each section's job | Does this section earn its place? |540| **Paragraph** | One idea per paragraph | What's the topic sentence? |541| **Sentence** | Clarity, precision | Can this be simpler? |542| **Word** | Precision, concision | Is this the right word? |543544### Phase 4: Feedback (2-4 weeks)545546| Feedback Source | What to Ask |547|-----------------|-------------|548| **Advisor** | Is the argument sound? Scope appropriate? |549| **Peer in field** | Is this interesting? What's missing? |550| **Peer outside field** | Is this clear? What's confusing? |551| **Writing group** | How's the prose? What drags? |552553### Phase 5: Polish & Submit554555- [ ] Format per venue requirements556- [ ] Check word/page count557- [ ] Verify all citations558- [ ] Anonymize if required559- [ ] Test figure readability at print size560- [ ] Submit before deadline (not AT deadline)561562---563564## Citation Integration565566### Weaving Citations Naturally567568| Pattern | Example | Use When |569|---------|---------|----------|570| **Narrative** | "Smith (2024) argues that..." | Discussing specific work |571| **Parenthetical** | "...has been demonstrated (Smith, 2024)" | Supporting a general claim |572| **Integrated** | "Smith's (2024) framework suggests..." | Referencing framework/concept |573| **Multiple** | "...is well-established (Smith, 2024; Jones, 2023)" | Broad support |574575### How Many Citations?576577| Section | Citation Density |578|---------|------------------|579| Abstract | 0 (usually) |580| Introduction | Medium (establish context) |581| Related Work | High (comprehensive review) |582| Methods | Low-Medium (justify choices) |583| Results | Low (your data, not others') |584| Discussion | Medium (connect to literature) |585586---587588## Handling Rejection589590### Reviewer Response Framework591592| Reviewer Says | What It Means | Response Strategy |593|---------------|---------------|-------------------|594| "Missing related work" | Gap in literature coverage | Add citations, explain positioning |595| "Claims not supported" | Evidence insufficient | Add data or soften claim |596| "Unclear methodology" | Can't assess validity | Expand method description |597| "Contribution unclear" | Buried or vague value | Make contribution explicit in intro |598| "Writing needs work" | Surface issues distract | Get editing help, revise prose |599| "Not right for venue" | Mismatch with audience | Try different venue, reframe |600601### Response Letter Template602603```markdown604# Response to Reviewers605606Dear Editors and Reviewers,607608Thank you for your thoughtful feedback on our manuscript "[Title]".609We have carefully addressed all comments and believe the paper610is significantly strengthened. Below we detail our responses.611612Major changes include:6131. [Summary of major change 1]6142. [Summary of major change 2]6153. [Summary of major change 3]616617---618619## Response to Reviewer 1620621### R1.1: "[Direct quote of concern]"622623We appreciate this observation. [Brief explanation of how you addressed it].624625Changes made:626- Section X, paragraph Y: [quoted new text or description of change]627- [Additional changes if needed]628629### R1.2: "[Next concern]"630631[Response pattern repeats]632633---634635## Response to Reviewer 2636[Same pattern]637638---639640We believe these revisions address all concerns raised. We are641grateful for the opportunity to improve our work.642643Sincerely,644[Authors]645```646647---648649## the AI assistant Assistance Commands650651### Draft Generation652653| Command | Action |654|---------|--------|655| "Draft a CHI paper on [topic]" | Generate CHI template with content |656| "Help me write the related work for [topic]" | Literature synthesis assistance |657| "Structure my HBR pitch about [finding]" | HBR framing guidance |658| "Turn dissertation chapter into journal paper" | Restructure and condense |659660### Review Assistance661662| Command | Action |663|---------|--------|664| "Review this abstract for CHI" | Venue-specific feedback |665| "Strengthen my contribution statement" | Clarify and sharpen |666| "Help me respond to reviewer concern: [quote]" | Response drafting |667| "Is my related work comprehensive for [topic]?" | Gap identification |668669---670671## Related Skills672673- [academic-research](../academic-research/SKILL.md) — Research methodology674- [knowledge-synthesis](../knowledge-synthesis/SKILL.md) — Literature synthesis675- [dissertation-defense](../dissertation-defense/SKILL.md) — Dissertation-to-paper pipeline676- [grant-writing](../grant-writing/SKILL.md) — Funding proposals677678## Falsifiability679680- This skill is not earning its tokens if drafts produced following its guidance fail peer review on structural grounds (section ordering, citation format, abstract structure) the skill explicitly addresses681- Stale if citation style guidance conflicts with current APA/IEEE/Chicago style guides682- Wrong if the academic conventions it documents are field-specific but presented as universal