Product & Planning

kirkruglov Bundle

Turn a folder of articles and industry clippings into a weekly trend signals brief for your product team. Use when preparing for planning sessions or roadmap reviews. Triggers: 'industry trend brief', 'trend signals from articles', 'тренд-бриф из статей', 'создай brief по трендам'.

kirkruglov Bundle

Generates a project charter from brief, stakeholder answers, and constraints. The charter is the first artifact of the Initiation phase. Once approved, it unlocks dependent tasks: generate-risk-register, generate-project-plan, generate-estimate. Accepts both structured briefs and free-form notes.

kirkruglov Bundle

Adapts any working document (PRD, status update, proposal, meeting notes) into audience-specific versions: Leadership/Executives, Engineering/Team, and Client/External partner. Applies audience-specific framing rules — business impact for executives, technical depth for engineers, outcome language for clients. Use when the same document needs to reach multiple audiences without manual rewriting. Triggers RU: «адаптируй документ», «сделай версию для руководства», «разные версии документа». Triggers EN: 'adapt document', 'stakeholder adapter', 'create executive version', 'make a client version', 'rewrite for audience'.

kirkruglov Bundle

Generates a communication plan from project charter, project plan, and stakeholder data. Includes stakeholder matrix (influence/interest), communication matrix, and escalation rules. Phase 2 artifact. In MVP stakeholders are extracted from charter; in P1 — from stakeholder-map.md.

apache Bundle

Print a human-readable index of every skill installed for this repository, grouped by the family each one declares, with the name to invoke it by and the first sentence of its `description`. Discovery is installation-aware: it covers a pinned snapshot install, the framework checkout, and marketplace plugin installs, so the index matches what the agent can actually run. Generated on every run from live `SKILL.md` frontmatter, so it never goes stale when skills are added, removed, or rewritten.

apache Skill

Read-only maintainer dashboard for the open general-issue backlog of <issue-tracker>. Surfaces a health rating, prioritised recommendations, age and staleness breakdowns, area pressure ranking, and a triage-funnel summary. Output is HTML by default; markdown fallback available.

apache Bundle

Read-only maintainer dashboard for the open-PR backlog of <upstream>. Surfaces a health rating, prioritised action recommendations, weekly closure velocity trends, area pressure ranking, and a triage-funnel breakdown — with the underlying area-grouped tables as a collapsible details section.

apache Skill

Sweep the open `<issue-tracker>` backlog for existing issues that could be labelled as good first issues. Classifies each candidate as READY (propose the GFI label), NEAR-MISS (surface edits to make it GFI-ready), or SKIP using the G1–G7 suitability rubric. Applies labels only after explicit maintainer confirmation; never edits issue bodies without the maintainer's direction.

apache Bundle

Draft a single net-new *good first issue* on the configured `<upstream>` repo from one supplied candidate such as a known gap or a small maintainer-named task. The skill first runs a suitability gate to confirm the candidate is small and newcomer-safe. If it passes the skill drafts one issue. The draft carries scope, code pointers, contributing-doc links, acceptance criteria, and an effort estimate. A readiness checklist gates the draft before it is shown. Nothing is filed via `gh` until the maintainer explicitly confirms. The skill never curates or relabels the existing backlog.

me2resh Skill

Capture a new product idea / feature concept / internal tool proposal to the ideas backlog (pre-triage).

me2resh Bundle

Self-contained HTML user-journey map (boxes/arrows with per-page modals) — preview between PRD and tech-design.

me2resh Skill

Update / create / reprioritise the product roadmap — add, remove, reorder milestones; renders a markdown table per milestone.

me2resh Skill

Write a feature spec or PRD from a problem statement or feature idea. Use when creating product requirements documents.

me2resh Skill

Generate a weekly / monthly / launch stakeholder update — synthesises PRs, closed issues, AgDRs, and roadmap into a narrative.

compozy Bundle

Creates a Product Requirements Document plus its companion user-story catalog (_user_stories.md) through interactive brainstorming with parallel codebase and web research. Use when starting a new feature or product, building a PRD, brainstorming requirements, or cataloging user stories and edge cases. Do not use for technical specifications, task breakdowns, or code implementation.

compozy Bundle

Creates a Technical Specification plus its companion test contract (_tests.md) by translating PRD business requirements into implementation designs through interactive technical clarification. Use when a PRD exists and needs a technical plan, when technical architecture decisions need documentation, or when a feature needs its exhaustive test-case catalog. Do not use for PRD creation, task breakdown, or direct code implementation.

leo-kuang-ai Bundle

Public workflow entrypoint (spec-prd): create, write, refine, or validate planning-readiness of brownfield PRD-grade requirements for existing systems before implementation planning. Do not use for 0-1 product exploration, unresolved product shape, HOW planning/task compilation, implementation/debug/review, lightweight direct fixes, generated runtime mirror edits, or PRD/design-source/source consistency audits; route to spec-brainstorm, spec-plan/spec-write-tasks, spec-work, review workflows, or spec-app-consistency-audit as appropriate.

leo-kuang-ai Bundle

Create or update STRATEGY.md. Use when starting a product, changing direction or roadmap, or when spec-ideate, spec-brainstorm, or spec-plan need upstream product grounding.

leo-kuang-ai Bundle

Build a throwaway prototype to answer an unresolved product behavior or visual question before implementation. Use when the question needs a runnable artifact and a human must experience it; do not use for product discovery (route those to spec-ideate or spec-brainstorm), routine polish, production implementation, or unattended runs.

leo-kuang-ai Bundle

Audit mobile App PRD/Figma/local-source consistency across page routes, KMP/Clean Architecture, components, analytics, i18n, engineering quality, and industry lenses before runtime validation; use for cross-source App consistency, not ordinary code review, PRD authoring, build/test execution, UI polish, or product-code edits.

jayrha Bundle

Writes strong OKRs (Objectives and Key Results) with outcome-focused, inspiring objectives and measurable, ambitious, time-bound key results. Use this skill when the user asks to write, draft, review, critique, or improve OKRs, goals, or quarterly/annual objectives, when they mention "objectives and key results", "set goals for the team", "turn this strategy into OKRs", "are these good key results", or when distinguishing outcomes from outputs/tasks for planning and performance.

jayrha Bundle

Produces a rigorous SWOT analysis (Strengths, Weaknesses, Opportunities, Threats) for a company, product, team, project, or personal decision, then converts the four quadrants into prioritized, concrete strategic actions using a TOWS cross-matrix. Use this skill when the user asks for a "SWOT analysis", "SWOT", "strengths and weaknesses", "competitive analysis", "strategic assessment", "situation analysis", "should we launch/enter/pivot", or wants help turning a SWOT into an action plan, strategy, or roadmap.

jayrha Bundle

Decomposes a goal into a work breakdown structure (WBS) with milestones, task dependencies, and effort estimates, then produces a schedule, critical path, and risk list. Use this skill when the user wants to plan a project, "break this down into tasks", build a work breakdown structure, create a project plan or roadmap, estimate effort/timeline, identify dependencies or the critical path, sequence work, or turn a goal/spec into an actionable, scheduled task list.

jayrha Bundle

Writes high-quality agile user stories that satisfy the INVEST criteria, with clear role/goal/benefit phrasing and testable Gherkin (Given/When/Then) acceptance criteria, and splits epics into thin vertical slices. Use this skill when the user asks to "write a user story", "create acceptance criteria", "break this epic into stories", "turn this requirement into a backlog item", "write Gherkin scenarios", or is grooming/refining a product backlog.

jayrha Bundle

Builds a realistic, personalized learning roadmap for a skill or subject — with milestones, curated resource types, active practice, spaced review, and progress checkpoints — fit to the learner's deadline and weekly time budget. Use this skill when the user asks to "make a study plan", "create a learning roadmap", "help me learn X in N weeks", "plan how to study for an exam", "build a curriculum", or wants a structured path to master a topic. Grounded in learning-science principles (spacing, retrieval, interleaving).

aiocean Skill

Synthesize discovery and dependency mapping into a step-by-step implementation plan via planner agent. Step 3 of the codeflow discover → map → plan trio (after aio-discover and aio-map).

aiocean Bundle

Markdown-based kanban board for AI agent task management. Board is a pure index (`.kanban/board.md`), every task lives in its own file (`.kanban/tasks/T-NNN-slug.md`). Use to init the board, add tasks, move them across Backlog/Todo/Doing/Done/Blocked, or archive completed work.

aiocean Skill

Read, create, and update Jira issues, sprints, and workflows plus Confluence pages via the Atlassian CLI. Use when the user mentions a Jira ticket key (e.g. PROJ-123), asks for a JQL/CQL search, wants to transition an issue, manage a sprint/backlog, or read/write a Confluence page.

aiocean Bundle

Author Workflow-tool scripts that spend effort like it's free and waste none of it. A maximal-effort playbook for multi-agent orchestration: choose an effort tier, then scale fan-out width, verification votes, and discovery rounds. Compose named amplifiers — multi-modal sweep, adversarial and perspective-diverse verify, judge panels, loop-until-dry discovery, completeness critic, synthesis — into a canonical harness. Use when authoring or editing a Workflow script, or when the user signals thoroughness: "exhaustive", "comprehensive", "thorough audit", "maximize", "spare no cost", "result-oriented orchestration".

annatchijova Skill

Enumerate the attack surface of an AUTHORIZED target and rank it into a reproducible, falsifiable candidate queue — reachability × asset value × technique plausibility — before anyone touches a payload. Use whenever the user asks "where should we start", "what's our attack surface", "what should we test first", "map the exposure", "prioritize these findings", "which endpoints matter", or hands over a recon dump, an asset inventory, a subdomain list, an OpenAPI spec, or a pile of scanner output and asks what to do with it. Also trigger when a security engagement is being scoped, when a pentest backlog needs ordering, or when a threat model needs candidate entry points. This skill produces a ranked queue of CANDIDATES with stated falsifiers — it never produces exploits, never asserts a vulnerability exists, and never scores by model intuition. Feeds red-team-auditing (confirm one candidate) and purple-team-exercise (measure detection for one technique).

themarmack Skill

Generate a one-page prep brief for a meeting from the user's notes + recent vault activity. Sections — meeting context, the participants (with their likely concerns, sourced from objection-response-library and people notes), the asks (what user needs to walk in prepared for), the prior context (relevant vault notes + decisions + facts), and the "if X comes up, here's the response" pre-empts. Use before any stakeholder meeting where the user wants to be ahead of the conversation rather than reacting to it.

themarmack Skill

Build a tailored demo script for an AI-coding / SDLC-modernization audience. Inputs — audience type (skeptical dev / curious leader / risk-focused auditor / vendor evaluator), demo goal (familiarization / objection-handling / specific-feature showcase / posture demonstration), time budget (10 / 20 / 45 minutes). Output is a moment-by-moment script with prep checklist, the specific Copilot prompts / commands the demoer will type, expected output narration, and the fallback plan if a step fails live. Use when prepping for a stakeholder demo, audit conversation, vendor-account-team meeting, or all-hands familiarization.

themarmack Bundle

Answer the recurring GitHub Copilot questions a regulated-environment GitHub admin fields daily (data handling, IP indemnity, content exclusions, audit logs, model selection, public code filter, knowledge bases, AGENTS.md governance). Reads canonical answers from `./canonical-answers.md` in this skill folder, applies them with the compliance-relevant lens, and cites GitHub's authoritative source. Also checks the Obsidian vault (`facts/copilot/*`) for any more recent fact that should override the canonical answer. Use whenever the user (or a stakeholder via the user) asks a Copilot policy / controls question.

themarmack Skill

Audit a GitHub repo or org's GitHub Advanced Security configuration against the org's baseline. Checks code scanning enablement, secret scanning + push protection, Dependabot alerts + version updates, dependency review, branch protection requiring GHAS checks, and CODEOWNERS hygiene. Uses `gh api` for live inspection of a target repo or org; falls back to documented baseline check items the user can run manually. Produces a structured finding list with severity, current vs expected state, and remediation steps. Use when the user asks to audit or review a repo's or org's GitHub Advanced Security (GHAS) configuration — code scanning, secret scanning + push protection, Dependabot, dependency review, branch protection — during repo onboarding, periodic GHAS audits, or before a stakeholder review of GHAS posture. This owns "is code scanning / secret scanning / push protection / Dependabot enabled?" questions at **repo or org** level. For researching how a single GHAS feature works use ghas-feature-research; for no

themarmack Skill

Collect what other major banks publicly share about their developer platforms, AI coding adoption, platform engineering, and SDLC modernization — engineering blogs (JPMorgan, Goldman Sachs, Morgan Stanley, Capital One, BofA, Wells Fargo, Citi, HSBC, Deutsche Bank, Barclays), conference talks (FS-ISAC, QCon Financial Services tracks), public RFCs / open-source projects, and named-analyst commentary. Output at vault/research/peer-bank/YYYY-MM-DD-{slug}.md. Composes with stakeholder-update-writer (exec asks "what are peers doing?") and decision-memo-writer. Use when the user asks what peer banks are publicly doing or saying about developer platforms, AI coding, or SDLC modernization — producing a fresh, cited research note from public sources only — not for evaluating a specific vendor's security posture (vendor-security-eval) or comparing AI coding tools (ai-coding-tools-compare).

themarmack Skill

Score a repo against the org's golden-path standards — CODEOWNERS, branch protection, required checks, signed commits, dependabot.yml currency, SECURITY.md, AGENTS.md, code-scanning enabled, secret scanning + push protection, license declared, README/CONTRIBUTING basics. Produces a 100-point scorecard with category subtotals and prioritized remediation. Use during repo onboarding, periodic sweeps of high-blast-radius repos, before a stakeholder review where you need a posture summary, or as the basis for an org-wide consistency report.