ai-native-workflow

Map AI and human tasks across Nebuchadnezzar v3.4 pipeline stages.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/WalkerVVV/firstmile-deals-pipeline --skill ai-native-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai-native-workflow
Source: https://github.com/WalkerVVV/firstmile-deals-pipeline/tree/main/.claude/skills/ai-native-workflow
Command: npx skills add https://github.com/WalkerVVV/firstmile-deals-pipeline --skill ai-native-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Jeff Su's AI-Native Workflow framework (4 Habits) mapped onto Nebuchadnezzar v3.4 infrastructure. Enables AI to draft, while humans decide timing and personalization.

Core Features & Use Cases

  • AI Breadcrumbs: link AI outputs to hubs and Git deal folders.
  • AI Swipe Files: stage-specific patterns and templates.
  • Task Mapping (YOU vs AI): decide which tasks are manual vs AI-driven.
  • Prompts Database: battle-tested prompts by use case.

Quick Start

Load the references/swipe-files for the stage, then use 4-habit prompts to map tasks before starting a stage.

Frequently Asked Questions about ai-native-workflow

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

FAQPage Schema
How do I eliminate misalignment between AI drafts and human decision-making in my workflow?

AI-native workflow reduces misalignment by enabling AI to draft while humans control timing and personalization. Map tasks between AI and human ownership, use stage-aware automation across discovery, rate creation, proposal, and win-back scenarios, and anchor outputs to Git and HubSpot for auditability.

What is task mapping and how does it help decide which tasks should be AI-driven versus manual?

Task mapping is a framework that explicitly labels each task as either human-owned or AI-driven based on stage and context. The workflow provides battle-tested prompts and swipe files for AI tasks, letting you control automation granularity while maintaining decision authority on personalization and timing.

How do I use swipe files and prompts to standardize AI output across stages?

Load stage-specific swipe files (patterns and templates) from the references component, then apply the 4-habit prompts before starting discovery, rate creation, proposal, or win-back work. This ensures consistent, battle-tested AI drafts anchored to your process.

Can I integrate AI breadcrumbs and cross-system logging with HubSpot and Git?

Yes. The workflow enforces cross-system logging to HubSpot and Git, linking AI outputs to deal folders via breadcrumb anchoring. This creates an auditable trail of AI-generated content tied to your CRM and version control.

Does this workflow support both exploratory and decisive AI modes?

Yes. The Nebuchadnezzar v3.4 pipeline includes blue pill (exploratory) and red pill (decisive) modes, allowing you to choose AI behavior based on stage, context, and risk tolerance while maintaining human oversight.

What's required before I start using this workflow in my sales or proposal process?

Set up access to the swipe-files references, map your stages to discovery, rate creation, proposal, and win-back scenarios, configure logging targets (HubSpot, Git), and establish which tasks will be AI-driven versus manual in your process.