CtrlK
BlogDocsLog inGet started
Tessl Logo

cindula/nextsteps

Intelligent next-steps engine with personality-driven suggestions. Generates dynamic, context-aware follow-up actions with expert mentorship tone, pattern recognition, and trust-building mechanics. Features 4 personality profiles (Friendly Expert, Chill Buddy, Straight Shooter, Thoughtful Mentor), confidence markers, and session continuity. Leverages persistent memory, self-improving preference learning, and concise signal-dense suggestions to psychically anticipate what users need next. Use when: (1) user completes a question or task, (2) user needs guidance on what to do next, (3) agent wants to proactively suggest trusted follow-up actions.

96

1.32x
Quality

94%

Does it follow best practices?

Impact

99%

1.32x

Average score across 5 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

task.mdevals/scenario-4/

Adding a Feature to a Node.js API

Problem/Feature Description

A backend team has been building a Node.js REST API for a SaaS product. A developer on the team has just implemented a new rate-limiting middleware and is asking their AI assistant for what to work on next. The assistant has memory files already set up from previous sessions, including some backlog items from earlier conversations.

The developer's message is: "Just merged the rate-limiting middleware into the API. It uses a sliding window algorithm and I tested it with Jest. What should I look at next?"

Your job is to generate a full response to this developer including a next steps section. Read the existing memory files before generating suggestions.

Output Specification

Produce the following files:

  • response.md — your complete response to the developer including the next steps section as it would be shown to the user

Input Files

The following files are provided as inputs. Extract them before beginning.

=============== FILE: .nextsteps/PREFERENCES.md ===============

NextSteps User Preferences

Schema Version: 2

Last Updated: 2026-03-20

Total Interactions: 14

Selection Rate: 57%

User Configuration

  • enabled: true
  • display-count: 4
  • min-count: 1
  • max-count: 7
  • preferred-categories: [all]
  • excluded-categories: []
  • format: standard
  • show-footer: true
  • include-backlog: true
  • include-lateral: true

Topic Affinities

  • nodejs: STRONG
  • testing: STRONG
  • api: MODERATE
  • security: MODERATE
  • deployment: MODERATE

Category Preferences

  • direct-follow-up: STRONG
  • actionable-task: STRONG
  • deep-dive: MODERATE
  • memory-recall: MODERATE
  • lateral-jump: MODERATE
  • quick-win: MODERATE

Anti-Preferences

  • ignored-topics: []
  • ignored-types: []

Behavioral Patterns

  • learned-display-count: 4
  • count-learning-confidence: HIGH

Gaps Detected

[none yet]

=============== FILE: .nextsteps/BACKLOG.md ===============

NextSteps Backlog

Format: - [DATE] [STATUS] brief-description (context: where-mentioned)

Statuses: OPEN, IN-PROGRESS, DONE, DISMISSED

Max active items: 30 (archive DONE/DISMISSED items when overflow)

  • [2026-03-18] [OPEN] Add OpenAPI/Swagger docs for the rate limit headers (context: API documentation discussion)
  • [2026-03-19] [OPEN] Set up staging environment deployment pipeline (context: DevOps planning session)
  • [2026-03-20] [IN-PROGRESS] Write integration tests for auth middleware (context: testing session)

=============== FILE: .nextsteps/HISTORY.md ===============

NextSteps Selection History

Format: [DATE] [EVENT-TYPE] details

Max entries: 50 (summarize oldest 25 when overflow)

Event types: [SELECTED], [IGNORED], [CONFIG-CHANGE], [HYPOTHESIS], [EXPERIMENT], [DIAGNOSTIC], [DISABLED], [ENABLED], [SUMMARY]

[2026-03-15] [SELECTED] #1 category: direct-follow-up, topic: nodejs [2026-03-15] [SELECTED] #2 category: actionable-task, topic: testing [2026-03-16] [IGNORED] none-selected, user-topic: debugging [2026-03-17] [SELECTED] #1 category: direct-follow-up, topic: api [2026-03-18] [SELECTED] #3 category: deep-dive, topic: security [2026-03-19] [SELECTED] #2 category: actionable-task, topic: deployment [2026-03-20] [CONFIG-CHANGE] property: display-count, old: 5, new: 4

evals

tile.json