跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
浏览器与自动化

analyze-project

Conduct SPARK methodology analysis for new project inception. Use at the beginning of a new project, when evaluating significant features, before bootstrap-project to validate viability, or when pivoting an existing project.

jrjsmrtn · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add jrjsmrtn/project-orchestration-skills --skill analyze-project

技能说明


name: analyze-project description: Conduct SPARK methodology analysis for new project inception. Use at the beginning of a new project, when evaluating significant features, before bootstrap-project to validate viability, or when pivoting an existing project. metadata: author: "Georges Martin jrjsmrtn@gmail.com" version: "0.1.34" license: MIT

SPARK Analysis

Conduct SPARK methodology analysis for new project inception.

When to Use

  • At the very beginning of a new project
  • When evaluating a significant new feature or system
  • Before running bootstrap-project to validate project viability
  • When pivoting or reassessing an existing project

What is SPARK?

SPARK is a structured inception methodology for validating project viability:

  • Stakeholders: Who is affected and who has influence?
  • Problem: What problem are we solving? What's the scope?
  • Analysis: What exists? What are the options? What are the constraints?
  • Risks: What could go wrong? How do we mitigate?
  • Knowledge: What do we know? What gaps exist?

Alternative Interpretation: Some practitioners use SPARK as: Situation, Proposal, Agreement, Resources, Kickers. This variant focuses more on proposal-driven inception where the situation is assessed, a proposal is made, agreement is sought, resources are identified, and potential "kickers" (deal-breakers or critical success factors) are surfaced early. Choose the interpretation that best fits your project context.

Required Inputs

  1. Project idea/concept (initial description)
  2. Context (why now? what triggered this?)
  3. Initial stakeholder list (who asked for this?)
  4. Time constraints (deadline pressures?)
  5. Budget/resource constraints (if known)

Workflow

Phase 1: Stakeholder Analysis

Identify and analyze all stakeholders:

## Stakeholders

### Primary Stakeholders (Direct Users)

| Stakeholder | Role | Needs | Influence | Engagement |
|-------------|------|-------|-----------|------------|
| [Name/Role] | [What they do] | [What they need] | High/Med/Low | [How to engage] |

### Secondary Stakeholders (Indirect Impact)

| Stakeholder | Interest | Impact | Communication |
|-------------|----------|--------|---------------|
| [Name/Role] | [Their interest] | [How affected] | [How to inform] |

### Key Questions to Answer
- Who will use this system daily?
- Who will maintain/operate it?
- Who funds/sponsors it?
- Who could block or derail the project?
- Who has domain expertise we need?

AI Assistance: Use Explore agent to research similar projects and identify commonly overlooked stakeholders.

Phase 1b: Create Audience Registry

Transform stakeholders into an Audience Registry - a standalone reference document that becomes the anchor for all downstream artifacts.

Create docs/reference/audience-registry.md:

# Audience Registry

Single source of truth for project audiences and their artifact needs.

## Audiences

| ID | Audience | Category | Needs | Derived Artifacts |
|----|----------|----------|-------|-------------------|
| A1 | [Role] | Primary | [Use the system for...] | BDD:user-*, Tutorial:*, C4:Person |
| A2 | [Role] | Integration | [Connect via...] | BDD:api-*, Reference:*, C4:ExternalSystem |
| A3 | [Role] | Operational | [Deploy/maintain...] | BDD:ops-*, Howto:*, C4:Operator |
| A4 | [Role] | Contribution | [Extend/maintain code...] | Explanation:*, C4:Component view |

## Category Definitions

| Category | Focus | Typical Roles | Primary Artifacts |
|----------|-------|---------------|-------------------|
| **Primary** | Using the system | End-users, consumers | Tutorials, User BDD, SystemContext |
| **Integration** | Connecting to the system | Developers, API consumers | Reference docs, API BDD, Container view |
| **Operational** | Running the system | Sysadmins, operators, SREs | How-tos, Ops BDD, Deployment view |
| **Contribution** | Extending the system | Contributors, maintainers | Explanation, ADRs, Component view |

## Traceability

Every artifact should reference an audience ID:
- BDD features: `@audience:A1`
- Documentation frontmatter: `audience: A1`
- C4 persons/actors map to Primary/Integration audiences

## Artifact Coverage Matrix

| Audience | BDD | Tutorial | How-to | Reference | Explanation | C4 Element |
|----------|-----|----------|--------|-----------|-------------|------------|
| A1 | [ ] | [ ] | - | - | - | [ ] |
| A2 | [ ] | - | - | [ ] | - | [ ] |
| A3 | [ ] | - | [ ] | - | - | [ ] |
| A4 | - | - | - | - | [ ] | [ ] |

---
*Created from SPARK analysis on [date]*
*Last updated: [date]*

AI Assistance: AI can suggest audience consolidation and identify gaps in artifact coverage.

Pattern Reference: See AUDIENCE-DRIVEN ARTIFACTS

Phase 2: Problem Definition

Define the problem clearly and scope boundaries:

## Problem Definition

### Problem Statement
[1-2 sentence clear statement of the problem]

### Current State
- How is this problem handled today?
- What pain points exist?
- What workarounds are people using?

### Desired Future State
- What does success look like?
- How will we measure success?
- What capabilities will exist that don't exist now?

### Scope Boundaries

**In Scope**:
- [Capability 1]
- [Capability 2]
- [Capability 3]

**Out of Scope** (explicitly excluded):
- [Excluded item 1 and why]
- [Excluded item 2 and why]

**Deferred** (future consideration):
- [Deferred item 1]
- [Deferred item 2]

### Success Criteria
1. [Measurable criterion 1]
2. [Measurable criterion 2]
3. [Measurable criterion 3]

AI Assistance: Use AI to challenge assumptions, identify edge cases, and ensure problem is well-defined.

Phase 3: Analysis

Analyze the landscape, options, and constraints:

## Analysis

### Existing Soluti
阅读完整来源 ↗