Project-management skills: Jira Epic and Story authoring pipeline, PRD-to-specs analysis, and per-repository Solution Design Document authoring
2 on GitHubby Nikolas Demiridisv0.4.2MITupdated 20 days ago
/
Plugin pm from marketplace nikolasd-plugins in nikolasd/nikolasd-plugins. Commands read from the repo's manifest — 19 days ago.
What it installs
Skills (7)
sdd
Creates or refreshes one living Solution Design Document (SDD) for the repository it runs in, filled against a template (the bundled Template v2.0, or one you supply as a file or Confluence page) and grounded in the code with file:line evidence. Interviews the user in batched passes, one per documen
epic-refine
Refines an existing Jira Epic with technical detail: runs a technical Q&A grounded in the codebase, then writes NFRs, personas, Technology Context, per-phase story tables, completion statements and sequence diagrams into the same Epic and advances its maturity to "Detailed Level Requirements Created
epic
Creates a new high-level Jira Epic through a business-level Q&A (Objective, Context, Scope, Success Criteria, Risks and Dependencies, delivery structure), optionally starting from a PRD or requirements document, and writes it to Jira only after the user confirms the full draft. Step 1 of the Epic pi
specs-from-prd
Turns a PRD into one local specs document. Checks the PRD's claims against the real code with file:line evidence, interviews the user about what it finds, and writes specs that are each sized as one small story under INVEST, with a feature-level design and every unresolved question recorded as a gap
story-from-document
Builds one fully detailed, code-verified Jira Story, with sub-tasks and Blocks links, from a Confluence page, a local document or a written brief (create mode), or fleshes out an existing Story key in place (promote mode). Checks the source's claims against the real repositories with file:line evide
story
Creates one Jira Story per run from an Epic's story table, as a child of that Epic, filling every Story section from the Epic content and from code it has read, then updates the Epic's story table and maturity. Step 3 of the Epic pipeline, after `epic` and `epic-refine`. Use `story-from-document` in
ui-mockups
Generates high-fidelity screen mockups for an existing Jira Epic, for business review and iteration (rendered PNG images, or a private Claude Design canvas when no browser is available), then writes a "User Interface Mockups" section into the Epic and advances its maturity to "UI Mockups Created". O
Personal workflow skills: session handoff, session reflection, plain-language writing style, spawning/controlling agents via Herdr, paired architect/engineer sessions, and a disciplined-delivery protocol for test-first, fully verified changes with per-action approval gates, and a code-grounded onboarding-documentation workflow
Airtable is the database and operations layer for your agents — whether running product, marketing, sales, ops, HR, or a custom business app. It combines structured data with multiplayer visual surfaces (grid, kanban, calendar, gallery, timeline) humans and agents share — plus sync integrations to Jira, Salesforce, Zendesk, Google Drive, Databricks, and the rest of your stack, all backed by enterprise governance. This plugin makes Claude fluent in Airtable: creating bases and schema, working with records, and sharing UI for collaboration. Bundles the official Airtable MCP server.
Airtable is the database and operations layer for your agents — whether running product, marketing, sales, ops, HR, or a custom business app. It combines structured data with multiplayer visual surfaces (grid, kanban, calendar, gallery, timeline) humans and agents share — plus sync integrations to Jira, Salesforce, Zendesk, Google Drive, and Databricks. Makes Claude fluent in Airtable: bases and schema, records, and collaboration UI. Bundles the official Airtable MCP server.
Break down epics into user stories with Humanizing Work split patterns.
1 skill
deanpeters/Product-Manager-Skills 8,001
Maintain pm?
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.