langadventurellc

@langadventurellc source repo

21 skills
0 followers
1 week ago last updated

▌
Issue Implementation · langadventurellc
Claims a single Trellis task and runs a plan-then-implement workflow — researches the task and parent feature, plans the implementation, writes the code, calls complete_task, and hands off to the paired reviewer teammate. Leaves changes uncommitted for review. Use when the user asks to "implement task", "claim task", or "work on task" by ID or scope. For multi-task feature orchestration, use task-trellis-teams:implement-trellis-issues instead.

1 install
▌
Create Trellis Issues · langadventurellc bundle
Orchestrates Trellis issue creation using Claude Code Agent Teams. Use when asked to "create trellis issues", "create and review issues", "create verified issues", or when you want issues created by a writer teammate and automatically reviewed by a reviewer teammate with direct-message fix loops.

1 install
▌
Issue Creation Review · langadventurellc
Verifies Trellis issues against original requirements for completeness, correctness, and appropriate scope. Use when asked to "verify issue", "validate trellis issue", "check issue completeness", or "review created issue".

1 install
▌
Create Jira Issue · langadventurellc
Creates a Jira issue in the project's configured Jira instance from a free-form description. Use when the user says "create a Jira ticket", "file a Jira issue", "open a Jira ticket", "log a bug in Jira", "make a new Jira ticket", or "report this in Jira". Drafts an outcome-focused summary and a structured description, humanizes the prose sections, shows the draft, and waits for explicit user confirmation before submitting.

1 install
▌
Implement Trellis Issues · langadventurellc
Orchestrates implementation of Trellis issues using Claude Code Agent Teams. Use when asked to "implement feature", "implement trellis issues", "execute feature with teams", "implement tasks via agent teams", or whenever an agent-teams-based implementation run is desired. The lead spawns a fresh developer/reviewer pair per leaf task; teammates coordinate review/fix cycles via direct SendMessage. Commits per wave by default; supports --no-commit, --no-docs, and --version flags. Recursive by default; unplanned non-leaf issues are skipped, never expanded.

1 install
▌
Manage Planning Team · langadventurellc
Internal skill. Runs inside the planning sub-session. Spawns a single-teammate investigation team to run investigate-jira-issue, then invokes create-trellis-issues to create Trellis issues from the artifact. Signals completion to the conductor when done.

1 install
▌
Issue Implementation Review · langadventurellc
Reviews code changes from a completed task implementation for correctness, completeness, and simplicity. Use when asked to "review implementation", "review task code", "code review", "verify implementation", or after completing an issue implementation.

1 install
▌
Investigate Jira Issue · langadventurellc
Investigate a Jira issue and turn it into a requirements or discovery document ready for implementation or Trellis issue creation. Use when the user asks to "investigate", "analyze", "look into", "scope", "break down", or "plan work for" a Jira ticket by key (e.g. ACME-1234). The skill fetches the ticket, pulls relevant linked context, then routes automatically to `planning:requirements-creation` (for ambiguous/underspecified tickets) or `planning:discovery` (for well-specified work needing research and analysis).

1 install
▌
Orchestrate Jira Issue · langadventurellc
Given a Jira issue key (e.g. ACME-1234), validates the issue then runs a planning sub-session (producing Trellis issues) followed by an implementation sub-session (opening a PR). Use when the user says "orchestrate", "run orchestration on", or "implement" a Jira issue via this plugin.

1 install
▌
Conduct Orchestration Team · langadventurellc
Internal skill. Manages the full lifecycle of one planning or implementation sub-session. Takes --team-type <planning|implementation>. Launches the sub, waits for hello handshake, sends instructions, waits for done signal from the manage-*-team skill, tears down.

1 install
▌
Manage Implementation Team · langadventurellc
Internal skill. Runs inside the implementation sub-session. Invokes implement-trellis-issues to implement all open Trellis tasks, then invokes create-pr to open a draft GitHub PR. Signals completion to the conductor when done.

1 install
▌
Configure Jira Orchestration · langadventurellc
Configure the Jira orchestration plugin's per-project settings — Atlassian base URL, cloud ID, and Jira project key. Use when the user says "configure jira orchestration", "set up jira orchestration", "set jira config", "update jira config", "change atlassian base url", "change cloud id", "change jira project key", or hits the missing-config pointer from /orchestrate-jira-issue, /create-jira-issue, or /create-pr. Loads the current values, lets the user fill in or update each one, and persists everything in a single write.

1 install
▌
Commit · langadventurellc
Commits staged and unstaged changes to git with a concise conventional commit message. Use when changes are ready to be committed, after completing a task, or when the user asks to commit.

1 install
▌
Discovery · langadventurellc bundle
Use when asked to "investigate", "analyze", "what would be involved", "scope this work", "research", "discover", "look into", "audit docs", or "research [tool/library]". Self-classifies the discovery type and dispatches to a playbook. Callers must not pass a subtype.

1 install
▌
Versioning · langadventurellc bundle
Bumps version files (package.json, plugin.json, pyproject.toml, Cargo.toml, VERSION, etc.) based on a diff. Project-type aware — Claude Code plugin markdown under agents/, skills/, commands/, hooks/, and .claude-plugin/ is treated as runtime configuration, not prose docs. Use when the user invokes /planning:versioning or when an orchestrator calls this skill at the end of an implementation run. Requires an explicit bump level or --infer — empty input is an error.

1 install
▌
Docs Updater · langadventurellc bundle
Reviews completed work and updates or creates project documentation (README, CLAUDE.md, AGENTS.md, .claude/rules/, docs/) to prevent stale docs. Invoked at the end of an implementation workflow with a base ref; diffs the working tree against that base to capture every change on the branch — committed and uncommitted.

1 install
▌
Humanize Text · langadventurellc
Rewrites technical text into plain English for a human reader. Use when an agent has produced prose that reads like implementation notes, or when the user asks to "humanize", "rewrite for humans", or "make this less technical" — for PR descriptions, ticket bodies, release notes, or code documentation. Returns only the rewritten text, ready to drop in.

1 install
▌
Requirements Creation · langadventurellc
Helps transform vague change requests into clear, structured requirements through targeted conversation. Use when a user has a change in mind for the codebase but hasn't fully articulated what they need — e.g. "we should add X", "improve Y", "fix the way Z works", "let's build a feature for...". Scales question depth to the complexity of the work. Produces an in-chat requirements summary suitable for handing to a ticket tool, a planner, another skill, or directly to an implementation agent.

1 install
▌
Issue Creation · langadventurellc bundle
Creates Trellis issues — projects, epics, features, or tasks — one hierarchy level at a time. Use when the user asks to create, decompose, or break down a project, epic, feature, or task in Trellis (e.g. "create a project", "create epics for P-…", "break down feature F-… into tasks", "decompose epic E-…"). Routes to the type-specific creation flow for the requested level only and stops there — does not auto-recurse to child levels.

1 install
▌
Create Implementation Plan · langadventurellc
Generates a detailed, actionable implementation plan for a non-trivial coding task. Invoked by the implementer (issue-implementation skill) at claim time when the claimed task does not meet the trivial-edit skip criteria. Returns an

1 install
▌
Issue Verification · langadventurellc bundle
QA-validates a completed Trellis issue by exercising the changed code the way it runs in production — drafts a test plan, gets user approval, then executes it and reports pass/fail/blocked. Use when asked to "QA", "verify", "validate the behavior of", "exercise", or "smoke-test" a completed Trellis task, feature, epic, or project by ID. This is verification via execution, not re-running the automated test suite.

1 install

21 published skills