This directory contains practical examples demonstrating Lash's task tracking features, from simple TODO lists to complex multi-file projects with dependencies.
File: 01-simple-todo.md
Complexity: Beginner
Concepts: Basic task structure, checkboxes, nested tasks, labels
A weekend TODO list showing Lash's minimal viable structure. Perfect for getting started.
lash show examples/01-simple-todo.mdWhat you'll learn:
- Basic task file structure (metadata, description, tasks)
- Task statuses:
[ ]open,[x]done,[-]waived - Simple nesting (parent-child tasks)
- Using labels for categorization
Directory: 02-multi-file-project/
Complexity: Intermediate
Concepts: Root index, multiple task files, cross-file dependencies, directory organization
A blog platform project split across backend and frontend task files.
cd examples/02-multi-file-project
lash list
lash graphWhat you'll learn:
- Organizing tasks across multiple files
- Using
index.lash.mdas project entry point - Cross-file dependencies with
@depends-on - Directory-based project structure
- Task completion logic across files
Structure:
02-multi-file-project/
βββ index.lash.md # Project overview
βββ backend/
β βββ database.md # Database tasks (complete)
β βββ api.md # API tasks (in progress)
βββ frontend/
βββ components.md # UI tasks (in progress)
Directory: 03-software-project/
Complexity: Advanced
Concepts: Microservices, cross-cutting concerns, team ownership, realistic complexity
A realistic e-commerce platform rewrite with 10 task files, 98 tasks, and complex dependencies.
cd examples/03-software-project
lash list --label backend
lash list --label security
lash graphWhat you'll learn:
- Managing large projects (10+ files, 100+ tasks)
- Cross-cutting concerns with labels (
#security,#performance,#testing) - Module dependencies (auth β catalog β orders β payment)
- Priority levels (
#p0,#p1,#p2) - Team ownership (
@owner) - Realistic estimates and timelines
- Compliance requirements (PCI-DSS, WCAG)
Structure:
03-software-project/
βββ index.lash.md
βββ backend/ # 4 microservices
β βββ auth-service.md
β βββ catalog-service.md
β βββ orders-service.md
β βββ payment-service.md
βββ frontend/ # 3 applications
β βββ component-library.md
β βββ customer-portal.md
β βββ admin-dashboard.md
βββ infrastructure/ # DevOps & observability
βββ k8s-setup.md
βββ cicd.md
βββ monitoring.md
File: 04-agent-workflow.md
Complexity: Intermediate
Concepts: AI agent integration, lash agent-prompt, agent best practices, token minimization
Demonstrates how AI agents (like Claude Code) should use Lash for task tracking.
lash show examples/04-agent-workflow.md
lash agent-prompt --label agent --label p0What you'll learn:
- Using
lash agent-promptfor focused context - Agent workflow: query β implement β validate β update
- Token minimization strategies
- Using
#agentlabels for agent-suitable tasks - Common agent mistakes and how to avoid them
- Error handling and recovery
- Adding discovered work during implementation
Key workflows:
- Agent gets context:
lash agent-prompt --label agent - Agent reads task:
lash show features/authentication.md - Agent implements feature
- Agent validates:
lash lint features/authentication.md - Agent marks complete and adds context notes
File: 05-complex-dependencies.md
Complexity: Advanced
Concepts: Deep nesting, blocked tasks, waived tasks, cross-file dependencies, circular dependency prevention
Shows advanced dependency patterns including 4-level nesting, blocked tasks [!], and cross-file dependencies.
lash show examples/05-complex-dependencies.md
lash graph --scope examples/05-complex-dependencies.md
lash check-linksWhat you'll learn:
- Deep task hierarchies (3-4 levels)
- Blocked tasks
[!]with external dependencies - Waived tasks
[-]for skipped work - Cross-file dependencies with
@depends-on - Task completion rules with complex dependencies
- Circular dependency detection and prevention
- Real-world dependency evolution
Dependency patterns demonstrated:
- Database migration system (4-level nesting)
- Distributed tracing (blocked tasks waiting on infrastructure)
- Feature flags (waived tasks, alternative approaches)
- Service authentication (cross-file dependencies)
- Performance optimization (progressive refinement)
File: contextual-notes.md
Complexity: Intermediate
Concepts: Contextual notes, requirements, acceptance criteria, implementation hints
Comprehensive guide to using plain bullet points (without checkboxes) for inline context.
lash show examples/contextual-notes.mdWhat you'll learn:
- Difference between tasks (
- [ ]) and notes (-) - When to use notes vs. child tasks
- Using notes for requirements and constraints
- Using notes for acceptance criteria
- Using notes for implementation hints
- Best practices for concise, useful notes
- How notes integrate with search and TUI
# Installation instructions will be here once published
cargo install lash- View an example:
lash show examples/01-simple-todo.md- List tasks in an example:
lash list --path examples/02-multi-file-project- See dependencies:
cd examples/03-software-project
lash graph- Generate agent prompt:
lash agent-prompt --label agent --label p0- Validate an example:
lash lint examples/01-simple-todo.md- Start with
01-simple-todo.md- Learn basic structure - Read
contextual-notes.md- Understand notes vs tasks - Explore
02-multi-file-project/- See multi-file organization
- Study
03-software-project/- See realistic complexity - Adapt structure to your needs
- Use labels for cross-cutting concerns
- Read
04-agent-workflow.md- Learn agent patterns - Practice with
lash agent-promptcommand - Implement agent-friendly task structure
- Review
05-complex-dependencies.md- Master dependencies - Learn
lash graphfor visualization - Use
lash check-linksfor validation
project/
βββ index.lash.md
βββ features/
βββ authentication.md
βββ user-profiles.md
βββ notifications.md
project/
βββ index.lash.md
βββ backend/
βββ frontend/
βββ infrastructure/
βββ design/
project/
βββ index.lash.md
βββ milestones/
βββ alpha.md
βββ beta.md
βββ release.md
- Design Document:
../docs/design-doc.md- Complete Lash specification - CONTRIBUTING.md:
../CONTRIBUTING.md- Project guidelines and conventions - Playground:
../playground/- PixelQuest game project demo
Have a great Lash example to share? Contributions welcome!
Guidelines for new examples:
- Include a clear README explaining what the example demonstrates
- Use realistic, practical scenarios
- Add contextual notes explaining key concepts
- Ensure all examples pass
lash lint - Progress from simple to complex concepts
- Include inline comments for educational value
- Check the design doc for detailed specifications
- Look at the playground for a full-scale example project
- Examine existing examples for patterns
Happy task tracking!