the-own-lab
40 verified skills
changelog-launch-post
Turn a CHANGELOG entry (or set of shipped commits) into a launch post draft for Twitter, a blog, or an email. Bridges engineering output to marketing output without requiring a marketing agent.
documentation
design-doc
Write a lightweight design doc before implementation for Medium/Large tasks. Mandates Non-Goals and Alternatives Considered sections to prevent scope creep and hindsight bias. Inspired by Google design doc culture.
development
decide
3-line ADR lite. Capture a decision you just made in under 60 seconds — problem, choice, rejected alternative. Complements the heavier `adr` skill; use this when a full ADR is overkill but the decision will be forgotten.
development
release-checklist
Pre-merge and pre-deploy checklist for solo-founder projects. Absorbs the former devops agent's gate role as a lightweight skill. Use before squash-merging to main and before promoting a build to production.
development
execute-plan
Execute an implementation plan step by step with verification at each step. Use when implementing code from an approved plan.
development
code-review
Structured code review with checklist covering logic, security, maintainability, and tests. Use when reviewing code changes before merge.
development
learn
Pipeline retrospective and pattern extraction for continuous learning. Use after every pipeline completion to capture lessons.
devops
git-worktree
Create and manage git worktrees for isolated development. Use when pipeline needs an isolated workspace.
development
requirements
Elicit and structure requirements through systematic questioning. Use when a feature needs to be scoped before design.
testing
critique-dialogue
/review Layer 3: Main Agent responds to every Layer 2 finding with a disposition. Hard cap 2 needs-user-decision per /review run.
testing
codebase-scan
Explore and understand codebase structure, patterns, and conventions. Use before making design decisions or diagnosing bugs.
development
pipeline-gate
Enforce pipeline progression rules — hard gates require user approval, soft gates auto-proceed on success. Use whenever a pipeline stage has a gate annotation.
devops
postmortem
Write blameless postmortems for significant bugs. Use after a bug fix to capture lessons learned.
documentation
weekly-ship
Weekly shipping ritual for solo founders. Scan the last 7 days of commits, draft a changelog entry, and pick next week's single top priority. Inspired by Duolingo's "Ship It" culture. Invoked via /ship-weekly.
development
success-metric
Force every feature spec to answer "how will we know this worked?". A single-field skill that gates feature requirements. Inspired by Duolingo's metric-driven culture — the solo-dev version of A/B testing discipline.
development
wireframe
Sketch low-fidelity UI wireframes before frontend work. Absorbs the former ui-designer agent's role as a skill. Uses Pencil MCP if available; otherwise produces an ASCII/markdown wireframe.
tools
read-brief
Command pre-step: load REQUIREMENTS/DESIGN/TODO + classify MEMORY into BRIEF.md. The only skill allowed to read MEMORY.md.
content-media
test-verify
Run and analyze test results against acceptance criteria. Use when verifying implementation completeness.
testing
security-scan
Scan code changes for security vulnerabilities. Use as part of code review or independently.
development
root-cause
Systematic root cause analysis for bug diagnosis. Use when investigating the underlying cause of a bug.
research
orchestrator
Company of One v2 orchestrator. Read this skill ONLY when a user message implies work (bug, feature, refactor, plan, ship) AND the task is Medium or Large. Do NOT read for questions, explanations, or Small tasks.
development
git-ops
Git branch, commit, and merge operations following project conventions. Use for all git workflow actions.
tools
adr
Write Architecture Decision Records for significant technical decisions. Use when a decision will affect future development.
development
write-plan
Write detailed implementation plans at file-level specificity. Use when breaking a design into executable steps.
testing
verify
Post-code check: run tests + confirm TODO acceptance items map to passing tests; applies a security lens but is not a separate scan.
development
session-reflection
/dev post-step: 9-question retro including Q9 prediction accuracy (ADR-002). Triggers reconstruction drill only for diverged core items.
development
debug-validate
/debug step: test one hypothesis at a time. Hard rule: no shotgun debugging — no concurrent changes across hypotheses.
development
adr-writing
Author an Architecture Decision Record under docs/projects/<project>/adr/. Only when a decision has cross-feature, immutable, long-lived consequences.
testing
clarify
Reverse-question the user until the feature intent is unambiguous. Drives brief Open Questions to empty before downstream skills run.
tools
debug-hypotheses
/debug step: enumerate 3–5 plausible root causes with explicit uncertainty labels. No padding.
development
explain-60-40
Split a feature into 60% boilerplate vs 40% Human-Owned Core; force the user to predict core behavior before Execute. Gates /dev per ADR-002.
development
red-team
/review Layer 2: adversarial review by reviewer agent reading ONLY REVIEW_INPUT.md. Three output buckets; security is a lens, not a separate skill.
testing
research
External-knowledge gathering step — Web Search + Context7 docs lookup. Validates that the spec/plan reflects current library reality.
development
spec-conformance
/review Layer 1 auditor + /think self-review. Three contexts: think-self-review, review-spec, review-implementation. Also judges reconstruction drills.
testing
spec-writing
Author REQUIREMENTS.md + DESIGN.md + TODO.md for a feature. The three files are one contract; they ship together.
content-media
tdd
Test-driven development cycle: RED → GREEN → REFACTOR. Every code change goes through it, including /debug regression tests.
development
test-plan
Decide WHAT to test before writing tests. Output: golden / edge / error / won't-test. Feeds tdd.
development
update-docs
Command post-step: write CHANGELOG + TODO once per command run. One call, not per-skill doc writes.
documentation
write-brief
Update BRIEF.md sections during a command run. Any skill that produces a brief-persisted artifact calls this to write it back.
documentation
saas-pricing
Pricing heuristics for solo-founder SaaS products. Use when designing or revising a pricing page, choosing a tier structure, or deciding between usage-based vs seat-based billing. Outputs a concrete pricing recommendation, not a lecture.
testing