القائمة
Plan new features to add to an existing onboarded project. Analyzes impact on existing modules, designs features that fit the current architecture, and ensures backward compatibility.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | add-features |
| description | Plan new features to add to an existing onboarded project. Analyzes impact on existing modules, designs features that fit the current architecture, and ensures backward compatibility. |
The user will describe what new capabilities they want.
Read docs/ARCHITECTURE.md, docs/FEATURES.json, docs/PLAN.md, docs/PROGRESS.md
For each requested feature: which existing modules are affected? New modules needed? Database schema changes? New dependencies? Conflicts with existing features?
For each new feature, following the existing architecture:
Append a "New Features" section with impact analysis and feature specs.
Append new features with F prefix IDs, status "not-started".
Do NOT modify any existing feature entries.
Log what was planned and recommend next steps.
Tell the user to switch to builder agent and run /next-feature.
Run a goal-bounded autonomous loop over the harness — select, build, verify, and commit features one at a time with a maker/checker split, an explicit stop-contract, and a per-run token/commit budget. Best run in the orchestrator agent.
Sync FEATURES.json and PLAN.md after architecture or scope changes mid-project. Preserves completed feature status while updating not-started features to align with the latest ARCHITECTURE.md and PLAN.md.
Initialize a new harness-managed solution project from a brief idea. Use when starting a brand new project. Creates docs/IDEA.md, docs/PLAN.md, docs/FEATURES.json, docs/ARCHITECTURE.md, docs/PROGRESS.md, AGENTS.md, and .github/copilot-instructions.md.
Design a feature before building it — research latest patterns, evaluate approaches, design APIs/data models/UI, and produce a technical design document. Use after /add-features and before the builder starts implementing.
Provide feedback on a design document and request changes. Use after /design-feature to iterate on the technical design before implementation begins. Supports multiple rounds of review.
Verify that the codebase follows the documented architecture. Checks for module boundary violations, circular dependencies, and cross-cutting concern leaks.
