Esp1ngard4
- 10 skills
- 0 followers
- 18 hours ago last updated
- ▌ Td Author · esp1ngard4Authors and audits Tool Definition (TD) documents and the SKILL.md paired with them — keeps the governance and reasoning (TD) separate from the operating instructions (SKILL.md), and enforces the document structure and version-history discipline. Use whenever a new tool is being created, a TD is being written or updated, a skill is being renamed or repackaged, an old tool version is being archived, or someone asks to review a tool's documentation for drift. Also use proactively on noticing a SKILL.md accumulating dated narration or changelog-style history, or a TD whose body has started describing what changed rather than how the tool works — that content belongs in the version history, and catching it early is this skill's job.
- ▌ Wbs Manager · esp1ngard4 bundleManages a work breakdown structure stored as a JSON register and generates an interactive HTML dashboard from it. Use whenever the user mentions "WBS", "work breakdown", "backlog", "roadmap items", or "deliverables", or asks to create or refresh a WBS dashboard, add or edit work items, or wants analytics on deliverables, backlog health, effort estimates or sprint allocation.
- ▌ Tsp Manager · esp1ngard4 bundleMaintains a TSP Register - the inventory of every Tool, System and Procedure you rely on - plus the recurring control activities that keep each one alive, and regenerates an HTML dashboard from it. Use whenever the user mentions a "tool register", "tool inventory", "process inventory", "TSP", or asks to add, retire or renumber a tool, record that a tool was reviewed, find which tools are obsolete or overdue for review, run a periodic controls check, or refresh the tool dashboard. Also use when a new tool or automation is created and needs registering.
- ▌ Raid Manager · esp1ngard4 bundleManages a RAID register - Risks, Actions, Issues, Decisions and Ideas - stored as a JSON register, and generates an interactive HTML dashboard with analytics and a risk heat map. Use whenever the user mentions "RAID", "risk register", "issue log", "decision log", or asks to add, edit or close a risk, action, issue or decision, to log an update or progress note against one, or wants a view of project risks and how the project is tracking.
- ▌ Content Review · esp1ngard4Report how a content sprint actually went — what was committed, delivered, outstanding and missed, plus how many items sit at each pipeline stage — and render a scope's plans as a visual roadmap. Use when someone asks how a sprint went, whether they are hitting their commitments, what is in flight, or wants to see the plan as a timeline or roadmap. Reads only; it never marks anything delivered or missed, and it holds no audience-response data.
- ▌ Content Plan Author · esp1ngard4Interview the author to turn a scope's decided position into dated, trackable work — audience, objective, the pillars in play, channels, and either a cadence or a set of commitments that can actually be missed. Use when a strategy exists and someone wants a plan, a campaign, a content calendar, or a commitment they can be held to, and when adding or amending a commitment on an existing plan. Runs only against an existing strategy file; it never invents a position.
- ▌ Content Post Writer · esp1ngard4 bundleInterview-led writer that turns notes into finished content without generic AI voice. Use when the user wants to (1) turn notes or drafts into a clean blog post, LinkedIn post, video storyboard, deck skeleton or poster copy, (2) interview themselves into a strong angle, (3) rewrite a draft to be plainer and more specific, (4) cut fluff and remove templated phrases, or (5) refine a draft over multiple rounds until final. Resolves the scope, plan and any due commitment before proposing an angle, and credits that commitment when the piece is locked. Saves to content-system/posts/YYYY-MM-DD-slug/ as a bundle — one backbone.md plus one file per artifact.
- ▌ Artifact Register · esp1ngard4 bundleManages Artifact Registers — the inventory of documents, folders, tools and physical items belonging to a scope, recording what each is, where it lives digitally and physically, what contains it, and which tool governs its contents. Use whenever the user mentions "artifact register", "document control list", "reference material", or asks where something is filed, what is in a folder, how to file a new document, what ID something should get, which artifacts are overdue for review, or to create a register for a project or area. Also use when the user asks whether the filing matches the register, since this tool reconciles a register against the actual folder on disk. Trigger too on "add this to the register", "is this filed correctly", "retire this document", or when a project accumulates enough documents to need its own register.
- ▌ Content Idea Capture · esp1ngard4Park a content idea in seconds before it evaporates, and manage the inbox of ideas waiting to be written. Use when someone says they have an idea for a post, wants to jot something down for later, asks what ideas are waiting, wants to start working one up, or wants to drop one. Captures in the author's own words without interviewing, sharpening, or asking for an angle — developing the idea is the writer's job, not this one's.
- ▌ Content Strategy Author · esp1ngard4Interview the author to decide a content strategy for one scope — the position it is built around, the pillars supporting it, what makes them credible, and what is deliberately excluded — and write it as a message house the drafting skill can read. Use when a scope has no strategy file, when an existing one needs rethinking, or when someone asks to set up positioning for a project or area of focus. Asks and records; it never decides positioning, and never derives it from what has already been published.