role-se

Codify SE role governance and Hands-on-Keyboard engagement workflows.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/JinLee794/L.C.G --skill role-se
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: role-se
Source: https://github.com/JinLee794/L.C.G/tree/main/.github/skills/role-se
Command: npx skills add https://github.com/JinLee794/L.C.G --skill role-se

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SE role management and HoK engagement require a structured, auditable framework to coordinate proof work, handoffs, and cross-role accountability.

Core Features & Use Cases

  • HoK positioning and governance across opportunities to ensure compliant, coherent customer engagements.
  • Milestone and activity tracking for proofs, demos, and handoffs, enabling auditable records.
  • BANT qualification and CSU handoff readiness to surface risks early and enable smooth transitions to delivery.

Quick Start

Outline your first HoK engagement plan for the target opportunity and identify the required legal and CSU handoff steps.

Frequently Asked Questions about role-se

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

FAQPage Schema
How do I structure Hands-on-Keyboard engagement for technical proofs and demos?

Hands-on-Keyboard engagement for technical proofs is structured by codifying SE role governance into a repeatable workflow that manages HoK positioning, legal clearance, and milestone tracking across solution engineering opportunities.

What is the best way to manage CSU handoff readiness and BANT qualification?

Managing CSU handoff readiness and BANT qualification requires capturing BANT evidence and maintaining milestone hygiene to surface delivery risks early and enable auditable, smooth cross-role transitions.

How do I create auditable activity-driven tasks for solution engineering milestones?

Auditable activity-driven tasks for solution engineering milestones are created by applying structured milestone and activity tracking across proofs, demos, and handoffs to ensure coherent and compliant customer engagement records.

Can I use a repeatable workflow to coordinate legal clearance for pilot programs?

Yes, a repeatable workflow coordinates legal clearance for pilot programs by positioning HoK engagements governance to ensure compliant, coherent customer interactions and cross-role accountability across the opportunity lifecycle.

Why do solution engineering handoffs fail without milestone hygiene and BANT evidence?

Solution engineering handoffs fail without milestone hygiene and BANT evidence because early delivery risks remain hidden, preventing smooth CSU transitions and breaking the auditable framework required for cross-role accountability.