القائمة
Implements a feature from its specification. Reads the spec, designs architecture, writes code, tests, and documentation. Use after a feature spec has been approved.
التثبيت باستخدام 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.
Creates a complete product feature specification. Use when defining new features, writing user stories, or planning product work. Generates structured specs in docs/specs/.
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.
| name | implement-feature |
| description | Implements a feature from its specification. Reads the spec, designs architecture, writes code, tests, and documentation. Use after a feature spec has been approved. |
| context | fork |
| agent | forja-dev |
Implement the feature: $ARGUMENTS
Follow these steps:
SIGN IN:
docs/adr/DESIGN:
BUILD (TDD Cycle): 4. For each piece of business logic: a. Red: Write a failing test that describes the expected behavior (Arrange-Act-Assert) b. Green: Write minimal code to make the test pass c. Refactor: Clean up — extract methods, improve names, remove duplication d. Verify each acceptance criterion from the spec has at least one test — if not, write one before proceeding 5. Implement infrastructure/adapters and write integration tests for critical paths 6. Scan for and remove any dead code you introduced or found
⏸️ TIME OUT — Run Implementation Complete Checklist (DO-CONFIRM): 7. Run through every item in the Implementation Complete checklist from your agent file 8. Fix any failures BEFORE proceeding
REFACTORING PASS: 9. Review all new code for code smells: long methods, feature envy, data clumps, primitive obsession 10. Apply Extract Method, Rename, Move as needed — leave code better than you found it
⏸️ TIME OUT — Run Pre-Delivery Checklist (DO-CONFIRM): 11. Run through every item in the Pre-Delivery checklist from your agent file 12. Fix any failures BEFORE proceeding
SIGN OUT: 13. Write the Handoff-to-Centinela using the communication checklist 14. Run the SIGN OUT checklist from your agent file