know

5-step workflow to add a feature to spec-graph with HITL clarification

Create a structured bug report for a feature with automatic tracking in todo.md

Structured 7-phase workflow for building features with discovery, exploration, design, implementation, and review

Create a structured change request for a feature with requirement tracking in spec-graph

Connect disconnected entities and cross-link spec-graph with code-graph

Archive a completed feature to .ai/know/archive/

Comprehensively expand and interconnect existing graphs to achieve 100% coverage

Show all planned, in-progress, and completed features grouped by phase

Walk through QA-based planning workflow to build complete product vision and spec-graph

Validate graph completeness before build by round-trip spec generation

Create graph files and populate project.md with context from the codebase

Interactive QA walkthrough for end-user acceptance testing of completed features

Design a custom schema for domain-specific graph modeling with the know tool

Check if codebase changes since feature creation warrant revisiting the plan

Implement an approved OpenSpec change and keep tasks in sync.

Archive a deployed OpenSpec change and update specs.

Scaffold a new OpenSpec change and validate strictly.

Use this agent when you need to estimate the implementation effort for a feature defined in the know spec graph. This includes: <example> Context: User has just added a new feature to the spec graph and wants to understand the scope. user: "I just added feature:real-time-sync to the graph. Can you estimate the work involved?" assistant: "I'll use the Task tool to launch the feature-effort-estimator agent to analyze this feature." <commentary>The user is asking for effort estimation of a feature, which is exactly what this agent does.</commentary> </example> <example> Context: User is planning sprint work and needs to prioritize features. user: "Before I start on feature:camera-feed, I want to know what I'm getting into." assistant: "Let me use the feature-effort-estimator agent to analyze the dependencies and complexity." <commentary>Understanding feature scope before starting work is a key use case for this agent.</commentary> </example> <example> Context: User mentions a feature and implicitly wants to understand effort. user: "What do you think about feature:multi-tenant-auth?" assistant: "I'll use the feature-effort-estimator agent to give you a comprehensive breakdown of what this entails." <commentary>Even when estimation isn't explicitly requested, understanding feature scope is valuable context.</commentary> </example>

Master the know CLI tool for managing specification graphs. Use when working with spec-graph.json, understanding graph structure, querying entities/references/meta, managing dependencies, or learning graph architecture. Teaches dependency rules, entity types, and graph operations.