strategy-builder

Construct strategy documents from repository metadata and user-defined goals.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/enuno/noesis-aeon --skill strategy-builder-enuno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: strategy-builder
Source: https://github.com/enuno/noesis-aeon/tree/main/skills/strategy-builder
Command: npx skills add https://github.com/enuno/noesis-aeon --skill strategy-builder-enuno

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of crafting a concise strategy document, allowing users to quickly create a north-star metric, priorities, audience, and hard constraints based on the project's goals and context.

Core Features & Use Cases

  • Automated Strategy Drafting: Generate a detailed strategy document from provided goals, repository content, and external links.
  • Customizable: Users can input structured briefs or use the Skill to infer strategy from existing repository information.
  • Use Case: Ideal for project managers or operators needing to quickly articulate the strategic direction of a project, leveraging the current state of the repository and the operator's intent.

Quick Start

Use the strategy-builder skill with the brief: strategy-builder | repo=myproject/repo | goal=launch MVP by Q3, iterate based on user feedback.

Frequently Asked Questions about strategy-builder

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

FAQPage Schema
How do I generate a project strategy document from repository metadata and goals?

To generate a project strategy document, you provide structured briefs with specific goals and repository names. The skill parses local READMEs, MEMORY.md files, and external links to infer and draft strategic priorities and north-star metrics automatically.

What is a north star metric and how is it defined during strategy creation?

A north star metric is the primary measure of a project's core value. During strategy creation, it is defined by parsing your stated goals and repository context, allowing the skill to articulate the strategic direction and key priorities.

Can I draft a targeted strategy without providing third-party API keys?

Yes, you can draft a targeted strategy without third-party API keys. The skill utilizes local file reads and Claude's WebFetch tool for external links, ensuring no external authentication is required to build your strategy document.

How do I set up a structured brief to build a strategy from my project goals?

You set up a structured brief using the syntax `strategy-builder | repo=myproject/repo | goal=launch MVP by Q3`. This input provides the necessary repository context and goal definitions to start the automated strategy drafting process.

Does this strategy builder work with existing README and MEMORY.md files to infer project direction?

Yes, the strategy builder works directly with existing README and MEMORY.md files. It reads this repository metadata to infer the current project state, helping to quickly articulate audience, hard constraints, and strategic priorities.

What are the limitations when using WebFetch for external links in repository analysis?

When using WebFetch for repository analysis, limitations include relying on Claude's built-in tool capabilities rather than direct third-party integrations. It fetches external link content to infer strategy but does not execute dynamic scripts or access authenticated endpoints.