nanlabs/nanlabs-delivery
PRD, TRD, ADR, work items, assessments, and delivery process
WHAT, Create and maintain Architecture Decision Records (ADRs) per the NaNLABS process in ClickUp. Covers when to write an ADR, required sections, review, and linking to epics/PRs. English for cross-team artifacts unless the user asks otherwise.
WHAT - Capture explicit agreements, terms, parties involved, dates, validity, and linked work items using the NaNLABS Agreement Document structure.
WHAT - Draft and review bugs using the NaNLABS Bug Template; classifies whether an issue should be escalated to incident based on production/user impact.
WHAT - Capture lightweight project, product, or operational decisions that do not require a full ADR; includes rationale, date, owner, and references.
WHAT - Default development workflow, task lifecycle, DoR, DoD, validation, and evidence model when a project has no explicit override. Repository instructions still take precedence.
WHAT - Draft and review epics using the NaNLABS Best Practices Epic Template; includes objectives, success criteria, related tasks, stakeholders, and effort metadata.
WHAT - Draft and review incident reports and RCA notes using NaNLABS Incident Management guidance; includes detection, impact, timeline, RCA, resolution, and follow-ups.
WHAT - Evidence-based management unit assessment for governance, delivery, collaboration, culture, and AI-native management readiness. Interactive and source-driven before any score is assigned.
WHAT - Create structured meeting minutes from notes or transcripts using NaNLABS meeting templates, with redaction, action items, decisions, and traceability.
WHAT - Planning, estimation, task breakdown, and iteration capacity fallback based on NaNLABS Best Practices. Use before finalizing backlog scope, story/task estimates, or iteration commitments.
WHAT, Draft and review a Product Requirements Document (PRD) from the NaNLABS ClickUp template. Business-level requirements, acceptance criteria, and traceability. Does not replace the product owner. English client-facing text unless the user asks otherwise.
WHAT - Interactive project assessment router: define scope and units, collect evidence via nanlabs-project-assessment-evidence, then delegate to technical or management unit assessment skills. Always evidence-based and human-reviewed.
WHAT - Interactive evidence intake for project assessments. Ask the user where each evidence source lives, build an evidence map, track missing evidence, assumptions, freshness, and confidence before any scoring happens.
WHAT - Produce spike and research findings using the NaNLABS spike template; captures purpose, findings, implementation strategy, risks, tradeoffs, open questions, and references.
WHAT - Draft and review technical tasks using the NaNLABS Best Practices Task Template; includes summary, technical notes, AC, estimate, owner, and due date.
WHAT - Evidence-based technical unit assessment for repositories, platforms, frontend, backend, infrastructure, data, UI/UX, and AI-native structural readiness.
WHAT, Draft and review a Technical Requirements Document (TRD) from the NaNLABS ClickUp template, typically after an agreed PRD. Covers architecture, data contracts, technical decisions, risks, and test strategy. English artifacts unless the user asks otherwise.
WHAT - Draft and review user stories using the NaNLABS task template plus the As a/I want/so that format from Best Practices examples.
WHAT - Router for creating and refining epics, user stories, tasks, bugs, and incidents using NaNLABS Best Practices work item hierarchy.