skills.rest
liminal-ai
liminal-aiOFFICIAL
Explore all skills by this author →
GitHub

ls-team-impl

Orchestrate story-by-story implementation with external CLI model verification.

1|1|Updated Apr 13, 2026
Search Tags:#logs#cli#verification#epics#orchestrate#team-management#story-by-story
One-click install
npx skills add https://github.com/liminal-ai/liminal-build --skill ls-team-impl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ls-team-impl
Source: https://github.com/liminal-ai/liminal-build/tree/main/references/full-liminal-spec-skills/ls-team-impl
Command: npx skills add https://github.com/liminal-ai/liminal-build --skill ls-team-impl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates end-to-end, story-by-story implementation using a distributed team and an external CLI model (Codex or Copilot). It ensures disciplined handoffs, verification, and state tracking across multiple stories in an epic.

Core Features & Use Cases

  • Orchestrates per-story implementation with a dedicated Opus teammate per story
  • Enforces formal verification gates and log-based state tracking
  • Supports on-demand resources and cross-team handoffs for complex epics

Quick Start

Run the orchestration skill to initialize a fresh team and begin with Story 1 using the chosen external CLI.

Frequently Asked Questions about ls-team-impl

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

FAQPage Schema
How do I manage story-by-story implementation across multiple epic stories?▼

Story-by-story implementation is managed by orchestrating a distributed team with a dedicated Opus teammate per story, enforcing formal verification gates and log-based state tracking to track progress across the epic.

Can I use external CLI models like Codex or Copilot for team orchestration?▼

External CLI models like Codex or Copilot are fully supported for team orchestration, providing the external-model verification and structured handoffs required to drive multi-story epic implementation.

How do I enforce verification gates and structured handoffs during implementation?▼

Verification gates and structured handoffs are enforced automatically during story-by-story orchestration, using log-based state tracking to ensure disciplined progress before advancing to the next story.

What's the best way to track progress across multiple stories in an epic?▼

Tracking progress across multiple stories in an epic is handled through log-based state tracking, which monitors formal verification gates and cross-team handoffs for each dedicated Opus teammate.

Do I need a dedicated teammate for each story in a multi-story epic?▼

A dedicated Opus teammate is assigned per story in a multi-story epic to ensure structured handoffs and formal verification gates are properly enforced throughout the implementation lifecycle.

When should I orchestrate implementation with an external CLI model instead of a single agent?▼

Orchestrating with an external CLI model is necessary for complex epics requiring distributed team management, cross-team handoffs, and formal verification gates that exceed a single agent's capacity.

Related Skills

Explore More Software Engineering Skills→
jaydubya818jaydubya818

bmad-create-epics-and-stories

Decompose PRD and Architecture requirements into mapped epics and stories.

Community
Advanced
IT-HUSETIT-HUSET
3

exec-plan

Execute plan pipelines by running exec-spec and quick-review per story.

Official
Advanced
liminal-ailiminal-ai
1

ls-team-spec

Orchestrate the Liminal Spec pipeline with agent teams and external verification subagents.

Official
Advanced
erankavijaerankavija

jit-execution-lead

Automate epic planning, execution, and quality control with AI agents.

Community
Advanced