Lia Creative
Official@Lia-Creative · Australia
Lia Creative provides a 73-skill product development lifecycle registry covering discovery, research, design, engineering, QA, and Linear ticket management for the Lia Tools line.
Agent Skills by Lia Creative
Showing 71 vetted skills indexed across 1 GitHub repositories.
toy-pickup
Loads scoped context files for Lia Tools sessions in a fixed read order.
toy-status
Assembles a live status table of Lia Tools toys from Linear, release registers, and vault records.
toy-feedback-ingest
Ingests toy feedback videos into vault meeting notes and Linear bug tickets.
toy-jam
Collects open jam items into an agenda and writes jam decisions back to strategy docs and Linear.
story-writer
Write user stories with Dan North narrative format and numbered Given/When/Then acceptance criteria.
research-problem
Researches the problem domain of a research plan with sourced evidence on prevalence, cost, and counter-cases.
wrap-up
Writes a structured After Action Report on the dispatch ticket to close a working session.
adventure-chat-ingest
Ingest recorded user conversations into a structured product discovery knowledge base.
plugin-manager
Reviews, merges, promotes, and rolls back skill changes for the lia-plugins marketplace.
research-schema-scrape
Recover the data model behind an existing product from its interface, exports, and documentation.
research-technology
Researches a technology's capabilities, limits, costs, failure modes, and licence terms from primary sources.
jtbd
Define jobs-to-be-done statements and map their requirements for epic planning.
research-competitors
Analyzes competitor capabilities, release cadence, pricing, and market overlap using captured UI evidence.
ticket-review
Validates whether a ticket is ready for an agent to start work without asking questions.
new-toy
Scaffolds new toy folders with lifecycle directories, README, and index housekeeping.
toys-digest
Drafts a weekly Slack digest of toy line board movement, feedback, and blockers.
testing-lead
Orchestrates QA test planning, case execution, hostile testing, and quality report verdicts for merged work.
ui-teardown
Captures product screenshots and produces evidence-cited UX teardowns with feature matrices.
review-and-merge
Reviews pull requests against numbered acceptance criteria and merges verified work.
toy-tidy
Audits the Lia Tools folder structure against its convention and reports or fixes drift.
ticket-builder
Creates and sequences grounded Linear tickets using MCP relations, labels, and priority conventions.
security
Checks code changes against security and data-compliance rules during build, review, and QA.
prototype-feedback-loop
Distills founder video walkthroughs of prototypes into structured docs and frame-attached tickets.
research-psychology
Research user motivation, anxiety, identity, and social context from studies and real accounts.
Frequently Asked Questions About Lia Creative
FAQPage SchemaWhat tasks can I run using Lia Creative's skills?▼
You can run the full product lifecycle: formalize problems and jobs-to-be-done, write epics and Dan North-style user stories, commission cited research across nine domains, explore and hand off hi-fi designs, build epics, run QA with test cases and adversarial rogue passes, and manage Linear backlogs and releases.
Who are these skills designed for?▼
They target founders, product managers, engineering leads, designers, and QA leads working on the Lia Tools product line. Stage-lead seats (discovery-lead, design-lead, engineering-lead, testing-lead, research-lead) coordinate specialist sub-skills, while ticket-writer and reviewer seats handle individual work items.
How does a typical session run in practice?▼
A session opens with toy-pickup or pickup to load tight context from the vault and Linear, executes through the relevant stage seat, and closes with wrap-up writing one After Action Report on the ticket. The project-manager skill moves tickets between stages on gate verdicts.
What are the prerequisites and dependencies?▼
Skills assume a Linear board via Linear MCP mechanics, an Obsidian-style vault under Products/Lia Tools, and the lia-plugins marketplace for distribution. UI capture uses Playwright for public pages and Claude-in-Chrome for logged-in pages; feedback ingestion requires a YouTube URL plus transcript.
How is quality and correctness enforced?▼
Execution-discipline mandates ground-truth rules, cold-start verification, and evidence-backed claims. Ready-review gates stories before build, review-and-merge verifies every acceptance criterion with an adversarial pass, and tester plus rogue execute planned and hostile test runs before any release promotion.