Imported from devplaninc/devplan-skills (skills/brief-with-devplan/SKILL.md). Install upstream with npx skills add devplaninc/devplan-skills --skill brief-with-devplan. Copyright stays with the author.

Product Pulse with Devplan

Name: brief-with-devplan
Author: devplaninc

Create a current Product Pulse for the requested product, project, or period. Lead with what changed, then show what is done, in progress, blocked, at risk, or awaiting a decision, with the evidence behind each important claim. End with the actions that need attention now.

When the user requests another kind of current brief, adapt the same evidence-backed structure to that scope rather than forcing a recurring update format.

Apply the devplan-product-context foundation skill when available. Let it handle retrieval, graph interpretation, evidence quality, and delivery-state checks. If it is unavailable, say so. Do not imply Devplan was checked.

Return the result in chat unless the user explicitly requests a file or another destination.

Use Devplan and connected sources as read-only unless the user asks for a specific change. Do not update work or send the brief without that request.

{ "ocm": "1", "id": "devplaninc-devplan-skills-brief-with-devplan", "kind": "skill", "name": "brief-with-devplan", "description": "Create a recurring Product Pulse or focused current brief using relevant changes, status, risks, evidence, people, and open decisions. Use for daily or weekly product updates, project reviews, planning sessions, launch discussions, meetings, or stakeholder updates, including requests asking what changed, what is done, in progress, blocked, at risk, or awaiting attention. Exclude one-customer product-context briefs, customer-release audience analysis, and deep audits of one known conflict or plan.", "publisher": "devplaninc", "version": "1.0.0", "capabilities": { "domains": [ "customer_support" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Create a recurring Product Pulse or focused current brief using relevant changes, status, risks, evidence, people, and open decisions. Use for daily or weekly product updates, project reviews, planning sessions, launch discussions, meetings, or stakeholder updates, including requests asking what changed, what is done, in progress, blocked, at risk, or awaiting attention. Exclude one-customer product-context briefs, customer-release audience analysis, and deep audits of one known conflict or plan." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/devplaninc/devplan-skills", "path": "skills/brief-with-devplan/SKILL.md", "ref": "cf5ff89f7dedc89b6524964ef9003bc68cb61790", "url": "https://github.com/devplaninc/devplan-skills/blob/cf5ff89f7dedc89b6524964ef9003bc68cb61790/skills/brief-with-devplan/SKILL.md", "key": "devplaninc/devplan-skills/skills/brief-with-devplan/SKILL.md" } }, "instructions": "# Product Pulse with Devplan\n\nCreate a current Product Pulse for the requested product, project, or period. Lead with what changed, then show what is done, in progress, blocked, at risk, or awaiting a decision, with the evidence behind each important claim. End with the actions that need attention now.\n\nWhen the user requests another kind of current brief, adapt the same evidence-backed structure to that scope rather than forcing a recurring update format.\n\nApply the `devplan-product-context` foundation skill when available. Let it handle retrieval, graph interpretation, evidence quality, and ", "cost": { "context_tokens": 232 } }

brief-with-devplan

About

Product Pulse with Devplan

Use it

Manifest

Reviews