piper-morgan-product

Execute one autonomous duty-cycle fire (START / WATCH / WORK / STOP) for a cycling agent. Invoked by the thin cron prompt on each fire. Use when a "DUTY CYCLE TICK" prompt fires, or to run a cycle fire manually. Holds the durable procedure so the cron prompt stays one-line.

Draft the Piper Morgan Weekly Ship newsletter from collected workstream memos. Use when PM says "draft the Ship", "draft Ship

Publish a finished blog post from this repo to the pipermorgan.ai website repo. Use when PM says "publish this post", "push to the blog", or when a draft is marked ready in the editorial calendar. Bridges piper-morgan → piper-morgan-website.

Update the editorial calendar CSV when PM reports a publication, new draft, status change, or URL. Use when PM says "published X on Medium", "add Y to the calendar", "update the URL for Z", or provides syndication URLs after a publish.

Delete a dead/fabricated module (or module family) without stranding importers, tests, CI jobs, or docs. Use for any fix-or-delete execution, Tier-3-style dead-code removal, or retiring a superseded subsystem. Encodes the Finish-the-Unfinished sprint's deletion lessons (Families 1-3, 2026-07-18/19).

Read GitHub Projects-v2 boards and issue state WITHOUT silent truncation or stale claims. Use whenever summarizing sprint/board state for PM, counting open items, or making any "N of M" claim about issues. Companion to assign-sprint-safely (which covers WRITES; this covers READS).

Safely assign a GitHub issue to a Sprint (or any Projects v2 single-select field) WITHOUT wiping other issues' assignments. Use when PM asks to set/change an issue's Sprint, Status, or other project-board single-select field. Encodes the per-item mutation and the hard "never full-replace the option list" rule that two agents have violated (1175 items wiped 2026-07-05).

Run a mechanical template audit on a finished blog draft before sending the publish-ready signal to Docs. Use after PM's voice pass is complete. Produces a pass/fail report with specific flags. Blocks the publish-ready signal on any FAIL.

Create or resume a session log at session start. Use when starting a new session, when PM assigns work, or after context compaction to find and continue your existing log. Critical for maintaining institutional memory.

RETIRED 2026-06-19 (post-migration,

Compile the cohort duty-cycle attention docs into a single, skimmable HTML rollup for the PM/CEO — what needs a decision, what's drift-worth-knowing, what's clean — with a live-state verification pass so the board reflects NOW, not a stale snapshot. Use when PM asks for the attention dashboard / rollup, on a duty-cycle fire that owns the rollup, or any time the cohort's open PM items need a single-glance summary. Originally a PA prototype; maintained by the Chief of Staff (Exec) as part of the org-attention oversight lane.

Draft a properly-formed GitHub issue for your project repo. Use when PM has a problem, bug, feature idea, or task to track. Produces a SLUG, structured body (Problem Statement / Goal / Requirements / AC), and correct metadata (priority, labels, milestone, epic). Trigger phrases: "file an issue", "create a ticket", "draft an issue", "track this", "we should file a bug for".

Turn a rough idea, brief, or conversation into a properly-formed feature spec / PRD — with problem statement, goals, non-goals, user stories, requirements, open questions, and success criteria. Piper grounds the spec in your project context. Trigger phrases: "write a spec for", "draft a PRD", "spec this out", "write this up properly", "I want to build X".

Scope a sprint from the GitHub backlog — review open issues, apply capacity and velocity, surface dependencies and risks, and produce a proposed sprint with rationale. Works without GitHub connector (manually-supplied backlog) but is significantly richer with it. Trigger phrases: "let's plan the sprint", "help me scope [sprint name]", "what should go in this sprint", "which issues should we tackle next".

Write a stakeholder update — progress, decisions, risks, next steps — calibrated to your audience (exec, team, investors, board). Draws on your project context. Trigger phrases: "write a stakeholder update", "draft an update for", "what should I tell [audience]", "write a status update".

Take raw user feedback — interview notes, survey responses, support tickets, session transcripts — and extract prioritized themes with recommendations grounded in your actual product. Trigger phrases: "synthesize this feedback", "what are users saying", "themes from these interviews", "analyze this feedback".

Surface what Piper learned when projects, features, or decisions reached

Show PM what trust tier Piper is at, what's unlocked at this tier, what's

Advance something from NOTICED to PROPOSED — surface a thing Piper

Generate a standard "Coding Agent" subagent prompt from a GitHub issue number. Use when deploying a coding subagent via the Task tool, when PM/Lead Dev says "brief a coding agent for

Refresh Piper's understanding of the PM's world when things have changed

Close a GitHub issue properly — update description checkboxes, add an

Triage and archive stale files from dev/active/. Use during session wrap-up, weekly audits, or when dev/active/ exceeds ~15 files. Prevents working directory from becoming a graveyard of superseded drafts.

Assess where the building-narrative blog sequence stands and decide the next move — draft the next beat or wait. Use BEFORE draft-blog-post whenever the task is to continue the building narrative: "what's the next beat", "continue the story", "review the logs since X and assess narrative beats", "where are we in the narrative", or any narrative-continuation/assessment work. Loads the conceptual model (linear-and-continuous, advance-the-front, narrative-vs-insight, wait-when-no-beat-has-formed) that templates don't carry, so the stance is right before any drafting. Hands off to draft-blog-post once a beat is confirmed.

Draft a blog post (narrative, insight, or Weekly Ship) for an editorial-calendar slot. Use when Comms is drafting a scheduled post, when PM hands off a slot, when starting from a source artifact (session logs, omnibus, Granola transcript), or when picking up an in-progress draft. Mandates a Phase 0 pipeline-inventory precondition (Layer C), carries voice discipline upstream from voice-pass to draft-time, applies the four-category opacity sweep before handoff, runs the verifiable-claims discipline at draft time, and enforces the calendar-row-at-draft-creation rule (Layer A) that prevents orphan drafts.

Close GitHub issues with proper evidence and audit-ready records. Use when completing work on a tracked issue, when PM says "close the issue", or before ending a session with completed work. Updates description checkboxes and adds closing comment.

Audit documentation surfaces for drift against recent code commits. Use after substantive code-shipping commits (feat/fix/refactor), at end-of-session sign-off, or when PM asks "are docs in sync?". Catches the "living documentation describing dead code" pattern before it accumulates.

Update BRIEFING-CURRENT-STATE.md when work changes project status. Any agent can use this after closing issues, completing gates, filing findings, or shipping features. Keeps the briefing fresh without waiting for Docs.

Check your agent mailbox for messages at session start. Use at the beginning of every session to review communications from other agents or advisors and note any action items.

Perform systematic audit-and-correct between phases of multi-step work. Use when PM says "audit cascade", before transitioning from issue to gameplan, gameplan to agent prompts, or prompts to execution. Catches drift before it accumulates.

Capture discovered work as tracking issues immediately. Use when you notice test failures, bugs, missing features, or technical debt during development. Prevents invisible work and ensures PM can prioritize appropriately.