lens-work-intake

Creates durable NextLens feature archives with lifecycle handoff and file-based work memory.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/crisweber2600/Lens.Core.Src --skill lens-work-intake-crisweber2600
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lens-work-intake
Source: https://github.com/crisweber2600/Lens.Core.Src/tree/main/_bmad/lens-work/skills/lens-work-intake
Command: npx skills add https://github.com/crisweber2600/Lens.Core.Src --skill lens-work-intake-crisweber2600

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Ideas, change requests, and related features often lose context when they live only in chat threads. This Skill turns a raw request into a durable, inspectable feature archive so decisions, constraints, and relationships survive across sessions and handoffs. ## Core Features & Use Cases - Feature Archive Creation: Generates a structured archive under the configured work path containing feature.yaml, work.md, memory.md, journey.md, handoff.md, and links.md with stable IDs and lifecycle metadata. - Related Work Linking: Scans nearby feature archives to record relationships like related_to, extends, replaces, and source_feature without bulk-copying prior memory. - Lifecycle Routing: Writes a handoff file pointing to the next command (/preplan, /expressplan, /next, /dev) and supports headless mode returning compact JSON. - Use Case: A user says "start work on adding SSO login" and receives a complete feature archive with goal, success criteria, durable memory, and a handoff to the planning phase. ## Quick Start Ask the assistant to run lens work intake to start a new feature archive for your idea or change request.

Frequently Asked Questions about lens-work-intake

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

FAQPage Schema
How do I start a new feature archive with lens work intake?

Invoke the skill with a request like 'start work' or 'create related feature' and describe your idea. It generates a kebab-case feature ID and writes the full archive (feature.yaml, work.md, memory.md, journey.md, handoff.md, links.md) under the configured work_intake_path.

What files does a NextLens feature archive contain?

Each archive contains feature.yaml for stable ID and lifecycle state, work.md for goals and success criteria, memory.md for durable decisions, journey.md for the lifecycle trace, handoff.md for the next workflow, and links.md for relationships and artifact paths.

Can lens work intake run in headless mode?

Yes. In headless mode it infers the feature ID, relationship, lifecycle track, and handoff from the request and existing artifacts, writes the archive, and returns compact JSON with status, feature_id, work_path, next_skill, and open_questions.

Does work intake modify sprint status, stories, or ledgers?

No. Intake only creates or updates the feature archive under the configured work path. Living ledgers, sprint status, story files, and implementation code remain owned by their dedicated Lens and BMad workflows such as lens-ledger-promotion.

How does intake handle related or follow-up work?

It scans nearby feature archives for feature.yaml, work.md, memory.md, and links.md, then records relationships using related_to, extends, replaces, source_feature, and belongs_to. It carries forward only durable decisions and constraints rather than bulk-copying prior memory.