okhp3-recurring-task-capture
OverKill Hill P³ · overkillhill.com · github.com/OKHP3
The intake mechanism. Turns "I just did this for the third time" into a structured artifact, not a lost observation.
Process
Extract the pattern. From the current conversation (or a description the user gives), identify: what was the task, what tools/skills were used, what was the input, what was the output, were there corrections or judgment calls along the way that would need to be encoded as instructions.
Assess readiness. Has this pattern stabilized enough to write down, or is this still "developing taste" (per the original delegation-contract framing — genuinely novel judgment calls each time means it's not a skill yet)?
- Not ready -> write a
docs/BACKLOG.md entry (date, task, times observed, candidate family, status: captured). Stop here.
- Ready -> continue to step 3.
Determine target family. Does this fit an existing family (mermaid/, linkedin/, or this repo's own process-capture/), or does it need a new top-level family? If new, note this explicitly — adding a new family directory is a bigger decision than adding a skill within one, and the user should confirm.
Produce the skeleton. Frontmatter (name, "pushy" description per skill-creator's triggering guidance) + section-header outline matching the body's intended structure, with 1-2 sentence descriptions per section and pointers to reference files that will need authoring. Match the structure of existing skills in this repo (core+domain pattern for multi-skill families, single-skill pattern for self-contained ones).
Update the index. Add the new skill's trigger row to root AGENTS.md, even though the skeleton isn't fully authored yet — mark it in the "Planned" section if the body is still mostly TOC, move to "Active" once authored.
Handoff
A skeleton from this skill is a starting point for skill-creator (the Anthropic example skill, if available) for full authoring, testing, and description-optimization — this skill does intake and structure, not iteration and evals.
About
Built by Jamie Hill · OverKill Hill P³
Published at github.com/OKHP3
Part of the OKHP3/skillz Agent Skill library.
MIT License -- free to use, fork, and adapt. A nod to the source is appreciated.
1---2name: okhp3-recurring-task-capture3description: Capture a recurring task as either a backlog entry or a new skill skeleton. Use when the user says "I keep doing X", "this is the third time", "make this a skill", "let's capture this", or at the natural end of a work session when a repeatable pattern just occurred. Extracts the pattern from conversation context (tools used, sequence of steps, input/output formats, corrections made) and produces either a BACKLOG.md line or a SKILL.md skeleton following this repo's conventions — not full skill authoring (that's skill-creator's job once a skeleton exists).4license: MIT5---67# okhp3-recurring-task-capture89**OverKill Hill P³** · [overkillhill.com](https://overkillhill.com) · [github.com/OKHP3](https://github.com/OKHP3)1011The intake mechanism. Turns "I just did this for the third time" into a structured artifact, not a lost observation.1213## Process14151. **Extract the pattern.** From the current conversation (or a description the user gives), identify: what was the task, what tools/skills were used, what was the input, what was the output, were there corrections or judgment calls along the way that would need to be encoded as instructions.16172. **Assess readiness.** Has this pattern stabilized enough to write down, or is this still "developing taste" (per the original delegation-contract framing — genuinely novel judgment calls each time means it's not a skill yet)?18 - **Not ready** -> write a `docs/BACKLOG.md` entry (date, task, times observed, candidate family, status: captured). Stop here.19 - **Ready** -> continue to step 3.20213. **Determine target family.** Does this fit an existing family (`mermaid/`, `linkedin/`, or this repo's own `process-capture/`), or does it need a new top-level family? If new, note this explicitly — adding a new family directory is a bigger decision than adding a skill within one, and the user should confirm.22234. **Produce the skeleton.** Frontmatter (`name`, "pushy" `description` per skill-creator's triggering guidance) + section-header outline matching the body's intended structure, with 1-2 sentence descriptions per section and pointers to reference files that will need authoring. Match the structure of existing skills in this repo (core+domain pattern for multi-skill families, single-skill pattern for self-contained ones).24255. **Update the index.** Add the new skill's trigger row to root `AGENTS.md`, even though the skeleton isn't fully authored yet — mark it in the "Planned" section if the body is still mostly TOC, move to "Active" once authored.2627## Handoff2829A skeleton from this skill is a starting point for `skill-creator` (the Anthropic example skill, if available) for full authoring, testing, and description-optimization — this skill does intake and structure, not iteration and evals.3031## About3233Built by [Jamie Hill](https://overkillhill.com) · [OverKill Hill P³](https://overkillhill.com)34Published at [github.com/OKHP3](https://github.com/OKHP3)35Part of the [OKHP3/skillz](https://github.com/OKHP3/skillz) Agent Skill library.36MIT License -- free to use, fork, and adapt. A nod to the source is appreciated.
OKHP3