القائمة
Create or update a feature flow document for end-to-end understanding of a feature.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/Abilityai/abilities --skill feature-flow-analysisيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Generate an agent-specific `/update-dashboard` skill that keeps `dashboard.yaml` current for Trinity. Analyzes the agent's purpose and data sources, proposes metrics, gets user approval, then scaffolds a schedulable skill.
Modify an existing playbook based on conversation context or explicit instructions. Use when user wants to update, fix, extend, or refine a playbook they already have.
Create a new skill or playbook. Guides through requirements gathering and generates the appropriate template based on complexity.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | feature-flow-analysis |
| description | Create or update a feature flow document for end-to-end understanding of a feature. |
| allowed-tools | Read, Write, Edit, Grep, Glob |
| user-invocable | true |
| argument-hint | <feature-name> |
| automation | manual |
| metadata | {"version":"1.0","created":"2026-03-13T00:00:00.000Z","author":"Ability.ai","changelog":["1.0: Initial version — creates or updates a feature flow document for end-to-end understanding of a feature."]} |
ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of
metadata.changelogabove — e.g.feature-flow-analysis vX.Y — recent: <summary>. Then proceed.
Create or update a feature flow document for end-to-end understanding.
| Source | Location | Read | Write | Description |
|---|---|---|---|---|
| Feature Flows Index | docs/memory/feature-flows.md | ✅ | ✅ | Flow index (keep minimal!) |
| Feature Flow Doc | docs/memory/feature-flows/{name}.md | ✅ | ✅ | Flow document |
| Frontend Code | src/frontend/ | ✅ | UI components | |
| Backend Code | src/backend/ | ✅ | API endpoints |
$ARGUMENTS - Feature name (e.g., "user-login", "payment-processing")If no feature name provided, ask for one.
Frontend (UI -> State -> API)
Backend (Endpoint -> Logic -> Data)
Side Effects (if applicable)
Include step-by-step testing instructions:
## Testing
### Prerequisites
- Services running
### Test Steps
1. **Action**: Do X
**Expected**: Y happens
**Verify**: Check Z
Write to: docs/memory/feature-flows/{feature-name}.md
CRITICAL: The index is for navigation, not documentation.
For NEW flows, add:
For UPDATED flows:
# Feature: {Feature Name}
## Overview
Brief description.
## Entry Points
- **UI**: `path/to/Component:line` - Action trigger
- **API**: `METHOD /api/endpoint`
## Frontend Layer
### Components
- `Component:line` - handler()
### State Management
- `stores/store` - actionName
## Backend Layer
### Endpoints
- `src/backend/routes/file:line` - handler()
### Business Logic
1. Step one
2. Step two
## Data Layer
- Query: description
- Update: description
## Side Effects
- Events: `{type, data}`
- Logs: event logged
## Error Handling
- Case -> HTTP status
## Testing
### Prerequisites
- Services running
### Test Steps
1. **Action**: X
**Expected**: Y
**Verify**: Z
## Related Flows
- [related-flow.md](feature-flows/related-flow.md)
Information density over completeness. Think debugging notes, not comprehensive docs.