PopNowAPI
Get API key

Kiro skills

Install PopNow skills in Kiro. Download a skill, unzip it into the skills folder, and call it by name in your next chat.

Browse 6 skills Kiro documentation
  1. 1Copy the install prompt

    Paste it into Kiro. It downloads the skill with your API key and unzips it into the right folder.

  2. 2Ask for the result

    Call the skill and say what you need in plain words: the topic, the audience, the length.

  3. 3Review and refine

    Open the file it made, ask for changes in the chat, and ship when it looks right.

All skills

  • Product Roadmap PresentationSlides

    Editable product roadmap presentation with checked inputs, evidence and speaker notes.

  • Design Proposal DeckSlides

    Editable design proposal deck with checked inputs, evidence and speaker notes.

  • Project Retrospective PresentationSlides

    Editable project retrospective presentation with checked inputs, evidence and speaker notes.

  • Innovation Strategy PresentationSlides

    Editable innovation strategy presentation with checked inputs, evidence and speaker notes.

  • Creative Brief PresentationSlides

    Editable creative brief presentation with checked inputs, evidence and speaker notes.

  • Decision Matrix VideoVideo

    A weighted decision film with cost direction, tie handling and sensitivity.

Give Kiro a product-planning presentation with clear evidence

Match the skill to the planning conversation

Kiro users can apply a presentation skill to turn product planning material into something stakeholders can discuss. Product Roadmap Deck is a useful option when sequencing and priorities are central. Design Proposal Deck is worth comparing when the decision is about a proposed direction, while Project Retrospective Presentation serves a review of completed work. These are distinct conversations. A roadmap should explain intended movement, a proposal should make the choice inspectable, and a retrospective should connect observed events to follow-ups. Select the skill from the decision on the meeting agenda, not just from the sample's colors.

Install the planning workflow at the intended scope

PopNow lists ~/.kiro/skills for Kiro's personal collection and .kiro/skills for a repository. Keep the package folder, SKILL.md and resources together, then use the plain skill name in a request such as popnow-product-roadmap-deck followed by the planning brief. Junie's listed project location is .junie/skills rather than .kiro/skills. That difference is useful to check when a team uses multiple assistants on the same repository. Sharing source documents does not automatically mean both assistants discover instructions from the same folder.

Keep plans separate from completed outcomes

A helpful Kiro brief supplies the audience, the decision required, source records and the status of each item. Mark dependencies and assumptions explicitly. For a retrospective, the catalog asks for chronological events and follow-up ownership; do not rewrite intentions as completed results. Request an outline before styling and review whether each slide helps the meeting reach its intended decision. If the output repeats vague planning language, add real milestones and evidence. If it fails to export, inspect local requirements independently of the content review. Optional generated visuals should reinforce a specific point rather than obscure missing information with a polished background.

Three ways to install

Install guides by agent

Same skills everywhere; only the folder changes.

Frequently asked questions

Which Kiro folder is appropriate for a team project?

The project location recorded here is .kiro/skills. Use the personal ~/.kiro/skills location for your own reusable collection. Keep the complete package under the chosen scope and make its role clear to teammates, without storing credentials or confidential meeting data inside shared instructions.

How do I choose between a proposal and a roadmap?

Use Design Proposal Deck when the audience must assess a proposed direction and its reasoning. Inspect Product Roadmap Deck when the discussion concerns priorities and sequencing over time. Provide the actual decision you need from the meeting so the selected workflow can organize relevant evidence.

What makes a retrospective brief useful?

Bring a chronological account of the work, source records and specific follow-up actions. Project Retrospective Presentation calls for ownership, due dates and completion evidence. Keep the discussion grounded in systems and observed events, and avoid filling gaps with unsupported conclusions about why something happened.

Why might a planning deck still feel generic?

A skill supplies a workflow, but it cannot supply the team's missing decisions. Add concrete milestones, dependencies, alternatives and evidence from the project. Ask Kiro to flag uncertain items for review before building the final presentation, then check whether the slides answer the meeting's central question.

Start building in minutes

One key for every model, a USD balance you top up when you need to, and an exact price before every run.

Get API key Try in Playground