Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
52 commits
Select commit Hold shift + click to select a range
2073e66
Disable openai telemetry when using ollama
meirborg Aug 12, 2025
2c4ab7d
Use full path to avoid claude errors when failing to resolve the path…
meirborg Aug 12, 2025
e446e17
Add support for LMStudio model provider
meirborg Aug 20, 2025
3eaa03a
Add command and agent systems to Nano CLI
meirborg Aug 26, 2025
f82939a
Add welcome message feature to interactive mode
meirborg Aug 26, 2025
5c3495d
Add YAML frontmatter support to agent files and enhance metadata hand…
meirborg Aug 26, 2025
43560d7
Enhance multi-provider support and configuration options
meirborg Aug 29, 2025
baf7561
Update default model and provider in constants.py
meirborg Aug 30, 2025
8a0440e
Enhance README and CLI with session management features
meirborg Aug 30, 2025
9525851
Refactor installation instructions and enhance API key checks
meirborg Aug 30, 2025
fcc6b0f
Improve error handling and user guidance in CLI
meirborg Aug 31, 2025
ca697a4
merge cursor-tools-mcp
meirborg Sep 9, 2025
12352ec
Remove unnecessary dependency on python-dotenv from project configura…
meirborg Sep 9, 2025
d2c4982
Enhance CLI functionality with tool call limits and new search features
meirborg Sep 9, 2025
f2be21e
Implement grep and file search tools with error handling
meirborg Sep 9, 2025
8b2d9aa
Remove outdated README_ALT.md and consolidate documentation in README.md
meirborg Sep 9, 2025
48a2a66
Fix terminal state handling and improve error detail display in inter…
meirborg Sep 9, 2025
e849569
Update evaluation results and enhance HOP/LOP documentation
meirborg Sep 9, 2025
a587a49
Add 'init' command to CLI for configuration setup and error handling …
meirborg Sep 9, 2025
6e6531f
Add development mode option and improve error handling in nano agent
meirborg Sep 9, 2025
ceacbbd
Revamp README documentation to reflect new features and enhancements
meirborg Sep 9, 2025
e84178a
release v0.3.0
meirborg Sep 10, 2025
9af0277
Update README and CLI for versioning and new search features
meirborg Sep 16, 2025
5eef670
Add new documentation and enhance event loop management in nano agent
meirborg Sep 17, 2025
f1f6b17
Refactor agent switching logic in interactive mode
meirborg Sep 17, 2025
1a25f74
Implement agent persona fixes and enhance HTTP client management
meirborg Sep 17, 2025
9456d13
Update version to 0.3.1 and add release notes for enhancements and bu…
meirborg Sep 17, 2025
5a19e3e
Add HOOKS.md documentation for the nano agent hooks system
meirborg Sep 17, 2025
8b1b892
Refactor nano-cli usage documentation and enhance CLI functionality
meirborg Oct 11, 2025
cbb4769
Update CLI documentation to standardize prompt execution with -p flag
meirborg Oct 11, 2025
79b3719
Enhance command evaluation feature and update version to 0.4.0
meirborg Oct 15, 2025
18616fb
Update command evaluation documentation and version to 0.4.1
meirborg Oct 15, 2025
50792f2
Fix shell command evaluation in interactive mode and clarify document…
meirborg Oct 16, 2025
fd99e27
Initial plan
Copilot Oct 24, 2025
f8ddbbf
Merge pull request #1 from meirm/copilot/add-user-tools-support
meirm Oct 24, 2025
5006f87
Refactor CLAUDE.md to Nano-agents and streamline documentation
meirborg Oct 24, 2025
e9fd231
Initial plan
Copilot Oct 24, 2025
3a1e42f
Add user-defined tools documentation to NANO_CLI_USAGE.md and CONFIG.md
Copilot Oct 24, 2025
9870b3b
Initial plan
Copilot Oct 24, 2025
f4e2368
Merge pull request #2 from meirm/copilot/add-user-defined-tools-docs
meirm Oct 24, 2025
6ede3bb
Add documentation for user-defined tools and allowlist
Copilot Oct 24, 2025
9827e3b
Merge branch 'main' into copilot/add-user-defined-tools-documentation
meirm Oct 24, 2025
79592c3
Merge pull request #3 from meirm/copilot/add-user-defined-tools-docum…
meirm Oct 24, 2025
8ac9c48
Update nano-agent version to 0.4.1 and add commands for listing and r…
meirborg Oct 24, 2025
25799e0
Refactor user-defined tools documentation for clarity and usability. …
meirborg Nov 1, 2025
7d6a331
Add Agent Skills management to CLI and core functionality
meirborg Nov 1, 2025
cba43b6
feat: Add Agent Skills system with built-in README Generator and Code…
meirborg Nov 1, 2025
217056d
chore: Bump version to 0.5.0 and add release notes skill documentation
meirborg Nov 1, 2025
861916b
feat: Add permission system for Skills and Commands, Security Audit s…
meirborg Nov 1, 2025
cc103da
Merge feat_allow_skills: Permission system for Skills/Commands, Secur…
meirborg Nov 1, 2025
d44d5fe
feat: Enhance README with Agent Skills documentation and examples
meirborg Nov 1, 2025
c7ca6ce
feat: Update nano-agent to version 0.5.3 and enhance installation script
meirborg Nov 1, 2025
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
218 changes: 218 additions & 0 deletions .agent-os/instructions/core/analyze-product.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,218 @@
---
description: Analyze Current Product & Install Agent OS
globs:
alwaysApply: false
version: 1.0
encoding: UTF-8
---

# Analyze Current Product & Install Agent OS

## Overview

Install Agent OS into an existing codebase, analyze current product state and progress. Builds on plan-product.md

<pre_flight_check>
EXECUTE: @.agent-os/instructions/meta/pre-flight.md
</pre_flight_check>

<process_flow>

<step number="1" name="analyze_existing_codebase">

### Step 1: Analyze Existing Codebase

Perform a deep codebase analysis of the current codebase to understand current state before documentation purposes.

<analysis_areas>
<project_structure>
- Directory organization
- File naming patterns
- Module structure
- Build configuration
</project_structure>
<technology_stack>
- Frameworks in use
- Dependencies (package.json, Gemfile, requirements.txt, etc.)
- Database systems
- Infrastructure configuration
</technology_stack>
<implementation_progress>
- Completed features
- Work in progress
- Authentication/authorization state
- API endpoints
- Database schema
</implementation_progress>
<code_patterns>
- Coding style in use
- Naming conventions
- File organization patterns
- Testing approach
</code_patterns>
</analysis_areas>

<instructions>
ACTION: Thoroughly analyze the existing codebase
DOCUMENT: Current technologies, features, and patterns
IDENTIFY: Architectural decisions already made
NOTE: Development progress and completed work
</instructions>

</step>

<step number="2" subagent="context-fetcher" name="gather_product_context">

### Step 2: Gather Product Context

Use the context-fetcher subagent to supplement codebase analysis with business context and future plans.

<context_questions>
Based on my analysis of your codebase, I can see you're building [OBSERVED_PRODUCT_TYPE].

To properly set up Agent OS, I need to understand:

1. **Product Vision**: What problem does this solve? Who are the target users?

2. **Current State**: Are there features I should know about that aren't obvious from the code?

3. **Roadmap**: What features are planned next? Any major refactoring planned?

4. **Team Preferences**: Any coding standards or practices the team follows that I should capture?
</context_questions>

<instructions>
ACTION: Ask user for product context
COMBINE: Merge user input with codebase analysis
PREPARE: Information for plan-product.md execution
</instructions>

</step>

<step number="3" name="execute_plan_product">

### Step 3: Execute Plan-Product with Context

Execute our standard flow for installing Agent OS in existing products

<execution_parameters>
<main_idea>[DERIVED_FROM_ANALYSIS_AND_USER_INPUT]</main_idea>
<key_features>[IDENTIFIED_IMPLEMENTED_AND_PLANNED_FEATURES]</key_features>
<target_users>[FROM_USER_CONTEXT]</target_users>
<tech_stack>[DETECTED_FROM_CODEBASE]</tech_stack>
</execution_parameters>

<execution_prompt>
@.agent-os/instructions/core/plan-product.md

I'm installing Agent OS into an existing product. Here's what I've gathered:

**Main Idea**: [SUMMARY_FROM_ANALYSIS_AND_CONTEXT]

**Key Features**:
- Already Implemented: [LIST_FROM_ANALYSIS]
- Planned: [LIST_FROM_USER]

**Target Users**: [FROM_USER_RESPONSE]

**Tech Stack**: [DETECTED_STACK_WITH_VERSIONS]
</execution_prompt>

<instructions>
ACTION: Execute plan-product.md with gathered information
PROVIDE: All context as structured input
ALLOW: plan-product.md to create .agent-os/product/ structure
</instructions>

</step>

<step number="4" name="customize_generated_files">

### Step 4: Customize Generated Documentation

Refine the generated documentation to ensure accuracy for the existing product by updating roadmap, tech stack, and decisions based on actual implementation.

<customization_tasks>
<roadmap_adjustment>
- Mark completed features as done
- Move implemented items to "Phase 0: Already Completed"
- Adjust future phases based on actual progress
</roadmap_adjustment>
<tech_stack_verification>
- Verify detected versions are correct
- Add any missing infrastructure details
- Document actual deployment setup
</tech_stack_verification>
</customization_tasks>

<roadmap_template>
## Phase 0: Already Completed

The following features have been implemented:

- [x] [FEATURE_1] - [DESCRIPTION_FROM_CODE]
- [x] [FEATURE_2] - [DESCRIPTION_FROM_CODE]
- [x] [FEATURE_3] - [DESCRIPTION_FROM_CODE]

## Phase 1: Current Development

- [ ] [IN_PROGRESS_FEATURE] - [DESCRIPTION]

[CONTINUE_WITH_STANDARD_PHASES]
</roadmap_template>


</step>

<step number="5" name="final_verification">

### Step 5: Final Verification and Summary

Verify installation completeness and provide clear next steps for the user to start using Agent OS with their existing codebase.

<verification_checklist>
- [ ] .agent-os/product/ directory created
- [ ] All product documentation reflects actual codebase
- [ ] Roadmap shows completed and planned features accurately
- [ ] Tech stack matches installed dependencies
</verification_checklist>

<summary_template>
## ✅ Agent OS Successfully Installed

I've analyzed your [PRODUCT_TYPE] codebase and set up Agent OS with documentation that reflects your actual implementation.

### What I Found

- **Tech Stack**: [SUMMARY_OF_DETECTED_STACK]
- **Completed Features**: [COUNT] features already implemented
- **Code Style**: [DETECTED_PATTERNS]
- **Current Phase**: [IDENTIFIED_DEVELOPMENT_STAGE]

### What Was Created

- ✓ Product documentation in `.agent-os/product/`
- ✓ Roadmap with completed work in Phase 0
- ✓ Tech stack reflecting actual dependencies

### Next Steps

1. Review the generated documentation in `.agent-os/product/`
2. Make any necessary adjustments to reflect your vision
3. See the Agent OS README for usage instructions: https://github.com/buildermethods/agent-os
4. Start using Agent OS for your next feature:
```
@.agent-os/instructions/core/create-spec.md
```

Your codebase is now Agent OS-enabled! 🚀
</summary_template>


</step>

</process_flow>

<post_flight_check>
EXECUTE: @.agent-os/instructions/meta/post-flight.md
</post_flight_check>
Loading