business-context

Load and consolidate project context from SOLUTION.md, GTM specs, and BUSINESS-CONTEXT.md.

5|2|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/NOMARJ/sigil --skill business-context-nomarj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: business-context
Source: https://github.com/NOMARJ/sigil/tree/main/packs/business/skills/growth/business-context
Command: npx skills add https://github.com/NOMARJ/sigil --skill business-context-nomarj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Load and unify project context for growth and business skills by aggregating SOLUTION.md, GTM specs, and fallback context, ensuring downstream skills have consistent grounding.

Core Features & Use Cases

  • Read SOLUTION.md first to extract project identity, product, and GTM details.
  • Fall back to BUSINESS-CONTEXT.md when SOLUTION.md is unavailable.
  • Return a compact, actionable context summary for downstream skills to consume.

Quick Start

Load the current project context by reading SOLUTION.md or BUSINESS-CONTEXT.md.

Frequently Asked Questions about business-context

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

FAQPage Schema
How do I load project context from SOLUTION.md for downstream growth workflows?

To load project context, the Skill reads SOLUTION.md first to extract project identity, product details, and GTM specs, then returns a compact context summary for downstream growth and business-strategy skills to consume.

What happens to project context loading when SOLUTION.md is unavailable?

When SOLUTION.md is unavailable, project context loading falls back to BUSINESS-CONTEXT.md to retrieve portfolio-level context, and can optionally incorporate GTM supplement data from the .nomark/gtm directory.

Does project context consolidation work with GTM planning and portfolio-level business strategy?

Yes, project context consolidation applies to growth and business-strategy skills across projects, portfolios, and GTM planning, ensuring downstream skills have access to identity, brand voice, buyer context, and the GTM motion.

Why do my downstream skills lack consistent identity and brand voice across different workflows?

Downstream skills lack consistent identity and brand voice because they operate without unified project context. Aggregating SOLUTION.md and GTM specs ensures all growth workflows share the same buyer context and project identity.

Can I use .nomark/gtm specs as a supplement to SOLUTION.md for context loading?

Yes, you can use .nomark/gtm specs as an optional supplement. The Skill satisfies the requirement to read SOLUTION.md as the primary source while optionally incorporating GTM supplement data from the .nomark/gtm directory.