Content Development Workflow
This document defines the development states for all content in this repository and provides prompts for moving content from one state to the next. The current state of every post is tracked in its YAML frontmatter under the status field.
States
| State | Owner | Entry Condition |
|---|---|---|
outline |
Nick | Thesis, key points, target tier, tone, and anecdotes captured |
draft |
AI + contractor | First full draft written; tags applied |
revision |
Nick + AI | Markup addressed; structure and argument finalized |
voice-edit |
Nick | Authorial pass complete — non-delegable gate |
production |
Contractor | Figures, social cards, and cross-posting copy ready |
scheduled |
Contractor | Queued in publishing pipeline with a confirmed date |
published |
— | Live on laneman.com; newsletter and social sent |
YAML Frontmatter Schema
Every post file must include the following frontmatter. Add tags at creation; update status at each transition.
---
title: ""
date: YYYY-MM-DD
status: outline # outline | draft | revision | voice-edit | production | scheduled | published
track: sgs # sgs | uw | acs | irs
secondary_tracks: []
book_chapters: [] # e.g. [uw_ch04]
tiers: [] # 1–8
themes: [] # spectrum-policy | wireless-technology | career | education | research
slug: ""
---Transition Prompts
Each prompt below is designed to move a post from one state to the next. Paste the prompt into a Claude conversation along with the post file. Update status in the frontmatter when the transition is complete.
outline → draft
What this does: Produces a first full draft from Nick’s outline. Applies voice calibration and content tags.
You are drafting a post for laneman.com. The author is J. Nicholas Laneman — professor, researcher, and entrepreneur. Read the outline below, then read the voice samples in voice-samples/ to calibrate tone before writing.
Instructions:
- Write a complete first draft from the outline. Do not pad or summarize; develop each key point fully.
- Match the voice in the samples: direct, precise, occasionally dry. No motivational filler. No generic openings.
- Target the tier(s) and audience specified in the frontmatter.
- Preserve the thesis exactly as stated in the outline. Flag any point where the outline is ambiguous rather than inventing a resolution.
- Verify that track, book_chapters, tiers, and themes in the frontmatter are correct given the content. Suggest corrections if needed.
- End with a one-paragraph note (not part of the draft) listing: (1) any outline points you found ambiguous, (2) any voice or tone judgment calls you made, (3) suggested figures or examples Nick may want to add.
When done, update status to `draft`.
[Paste outline here]draft → revision
What this does: Reviews the draft for structure, argument, voice, and tag completeness. Produces a marked-up version with inline notes for Nick to act on.
You are reviewing a post draft for laneman.com. The author is J. Nicholas Laneman. Read the voice samples in voice-samples/ before reviewing.
Instructions:
- Read the full draft, then provide inline comments using the format [NOTE: ...] at the point in the text where each issue occurs.
- Flag: weak or generic sentences, argument gaps, places where the voice drifts from the samples, transitions that don't land, and any section that could be cut without loss.
- Do not rewrite sentences unless a rewrite is strictly necessary to illustrate the problem — prefer describing the issue.
- After the marked-up draft, provide a short summary (bullet list, no more than 8 items) of the highest-priority changes Nick should make before this goes to voice edit.
- Verify frontmatter tags are complete and accurate. Flag any that are missing or wrong.
- Do not change status. Nick will update to `revision` after reviewing your notes and confirming the draft is ready for his markup pass.
[Paste draft here]revision → voice-edit
What this does: Summarizes what changed in revision and prepares a clean handoff document for Nick’s voice edit.
You are preparing a post for Nick's voice edit. This is the non-delegable authorial pass — your job is to make it easy for Nick to move efficiently.
Instructions:
- Provide a clean version of the revised draft with no inline comments or markup.
- Above the draft, write a short handoff note (3–5 bullets) covering: (1) what changed significantly from the first draft, (2) any structural decisions that were made and why, (3) any sentences or passages that are still uncertain and may need Nick's judgment, (4) any open questions that need a decision before production.
- Do not suggest edits. This section of the process belongs entirely to Nick.
- Update status to `voice-edit` in the frontmatter.
[Paste revised draft here]voice-edit → production
What this does: Generates a production brief for the contractor — figures needed, social variants, and newsletter placement — from Nick’s final draft.
You are preparing a production brief for a contractor. Nick has completed his voice edit and this post is ready for production. Read the final draft below and generate the following:
1. **Figures and visuals**: List any figures, diagrams, or images the post requires or would benefit from. Be specific about what each should show. Mark each as Required or Optional.
2. **Social variants**:
- LinkedIn: 150–250 word post. Open with the sharpest sentence from the draft. No hashtags. Link to the post.
- X/Twitter: One punchy sentence (under 280 characters) that earns the click. No hashtags.
- Newsletter teaser: 2–3 sentences for the weekly newsletter. Treat the reader as intelligent; do not summarize — intrigue.
3. **Newsletter placement**: Suggest where this post fits in the weekly newsletter (lead story, secondary item, or brief mention) and why.
4. **Cross-posting notes**: Flag any content that needs adjustment before posting on a specific platform (e.g., ND IP §2.3.2 exposure, audience mismatch).
5. **Checklist for contractor**:
- [ ] Figures created and attached
- [ ] Social copy approved by Nick
- [ ] Newsletter slot confirmed
- [ ] Publishing date confirmed
- [ ] Post file status updated to `production`
[Paste final voice-edited draft here]production → scheduled
What this does: Confirms production is complete and records the publishing date in frontmatter before the post enters the queue.
Production is complete for this post. Update the frontmatter as follows:
1. Set `status` to `scheduled`.
2. Add a `publish_date` field (YYYY-MM-DD) with the confirmed publishing date.
3. Add a `newsletter_issue` field with the issue number this post appears in, if applicable.
4. Confirm all other frontmatter fields (track, book_chapters, tiers, themes) are final.
Return only the updated frontmatter block. Do not modify the post body.
[Paste frontmatter here]scheduled → published
What this does: Final archival update after the post goes live.
This post has been published. Update the frontmatter as follows:
1. Set `status` to `published`.
2. Confirm `date` matches the actual publish date (update if the schedule slipped).
3. Add a `url` field with the canonical URL on laneman.com.
4. Add a `newsletter_issue` field if not already present.
Return only the updated frontmatter block. Do not modify the post body.
[Paste frontmatter here]Notes for Contractors
- The
statusfield is the source of truth for where a post is in the pipeline. Always update it when you complete your step. - Never publish to any platform without explicit confirmation from Nick — this applies to the website, newsletter, and all social channels.
- Voice samples in
voice-samples/are the calibration reference for all drafting. Read them before writing. - If you encounter a post that references Notre Dame commercially (e.g., uses “Notre Dame” in a way that promotes a product or course), flag it for Nick before production. ND IP §2.3.2 requires written permission for commercial use of the name.
- Subscriber data, course rosters, and any student-identifiable information never go in this repository. Route those to LanemanOps.
Last updated: June 2026