القائمة
Creates a complete product feature specification. Use when defining new features, writing user stories, or planning product work. Generates structured specs in docs/specs/.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Post-implementation business assessment by Prometeo (PM). Verifies success metrics achievement, scope compliance, acceptance criteria business interpretation, risk materialization, and product decision closure. Outputs structured report with verdict and confidence score.
Analyzes checklist effectiveness by tracking hit rates, identifying stale items, and finding coverage gaps. Generates evolution suggestions following Boorman's principles. Use periodically to keep checklists field-tested and relevant.
Scans the codebase for dead code, tech debt, outdated dependencies, and code quality issues. Use periodically or before releases to maintain code hygiene.
Generates test cases for a module or function following FIRST principles and Arrange-Act-Assert pattern. Detects test framework from project config. Use to bootstrap test coverage for existing code or as the Red phase of TDD.
Create and manage git worktrees for isolated feature work. Use when starting implementation that should not touch the main workspace, or for parallel development. Handles creation, baseline verification, and cleanup.
Implements a feature from its specification. Reads the spec, designs architecture, writes code, tests, and documentation. Use after a feature spec has been approved.
| name | feature-spec |
| description | Creates a complete product feature specification. Use when defining new features, writing user stories, or planning product work. Generates structured specs in docs/specs/. |
| context | fork |
| agent | prometeo-pm |
Create a feature specification for: $ARGUMENTS
Follow these steps:
SIGN IN:
TIER SELECTION:
RESEARCH (READ-DO):
3. Read existing specs in docs/specs/ to understand current patterns and avoid conflicts
4. Identify dependencies on existing features or systems
BUILD:
5. Create the spec at docs/specs/{feature-name}.md using the tier-appropriate template from your system prompt
6. For each user story, validate against INVEST:
TIME OUT -- Run Spec Completion Checklist (DO-CONFIRM): 8. Run through every item in the Spec Completion checklist from your agent file 9. Fix any gaps BEFORE proceeding
SIGN OUT: 10. Write the Handoff-to-Forja using the communication checklist 11. Run the SIGN OUT checklist from your agent file
