vibe-to-agentic-framework

Define the official framework for the Vibe Coding to Agentic Engineering presentation.

Updated May 22, 2026
One-click install
npx skills add https://github.com/shekerkamma/peopletech-marketplace --skill vibe-to-agentic-framework-shekerkamma
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vibe-to-agentic-framework
Source: https://github.com/shekerkamma/peopletech-marketplace/tree/main/plugins/presentation-suite/skills/presentation/vibe-to-agentic-framework
Command: npx skills add https://github.com/shekerkamma/peopletech-marketplace --skill vibe-to-agentic-framework-shekerkamma

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates inconsistent narrative, misaligned slide sequencing, and incorrect journey level assignments in the "Vibe Coding to Agentic Engineering" presentation by providing the official, canonical conceptual framework and pedagogical guidelines for the PeopleTech AI Engineering team.

Core Features & Use Cases

  • 4-Level Journey System: Defines the Low/Medium/High/Pro journey levels with color coding, slide inheritance rules, and transition reference table for consistent level tagging across all slides.
  • Pedagogical Sequence: Outlines the deliberate 6-part structure of the presentation, including slide groupings, level assignments, and concept dependencies to ensure logical knowledge building.
  • TodoApp Running Example: Provides the official before/after TodoApp project structure to make abstract agentic engineering concepts tangible for the audience.
  • Use Case: A team member creating a new slide about custom Claude Code agents can use this Skill to confirm the slide belongs in Part 6 (Agentic Engineering), is tagged with the High journey level, and uses the correct TodoApp example to illustrate the concept.

Quick Start

Use this skill to verify that your new slide about CLAUDE.md project memory rules is correctly placed in Part 3 (Project Memory) and assigned the Medium journey level.

Frequently Asked Questions about vibe-to-agentic-framework

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a vibe coding to agentic engineering presentation for consistent slide sequencing?

Structure your presentation using a 6-part pedagogical sequence with a 4-level journey system. This framework ensures logical knowledge building by defining slide groupings, concept dependencies, and consistent level tagging across all slides.

What are the journey levels in agentic engineering and how do I assign them to slides?

The journey levels in agentic engineering are Low, Medium, High, and Pro. You assign them using color coding and slide inheritance rules, referencing a transition table to maintain consistent level tagging throughout the presentation.

How do I use a TodoApp example to explain claude-code project memory rules?

Use the official before-and-after TodoApp project structure provided by the framework to make abstract claude-code concepts tangible. This ensures example consistency when illustrating project memory rules during your presentation.

Where should I place a slide about custom Claude Code agents in an agentic engineering presentation?

Place slides about custom Claude Code agents in Part 6 of the presentation, which covers Agentic Engineering. You should also tag these slides with the High journey level to maintain the correct narrative arc.

Can I use this framework to check if my presentation slides have misaligned journey level assignments?

Yes, you can use this framework as a single source of truth to perform consistency checks on slide placement and journey level assignments. It eliminates incorrect level tagging by providing transition rules and inheritance guidelines.

What is the best way to organize a team's presentation editing workflow for vibe coding concepts?

Organize your editing workflow around the framework's 4-level journey system and 6-part pedagogical sequence. This provides a canonical structure for slide placement, level assignment, and running example consistency across the team's presentation.