maestro-spec

You can record project coding standards using natural language intent. The skill infers the category and scope from your description, converting it into a structured spec entry for your project rules without requiring rigid command grammar.

Capturing architecture constraints is best handled by inferring category and scope from plain text. This approach automatically classifies rules like service communication protocols into a structured spec log, keeping reusable knowledge separate from project constraints.

Yes, you can enforce code review rules by adding them through plain text descriptions. The system automatically infers the rule category, such as review or testing, and appends the structured entry to your project spec log for team workflows.

To separate reusable knowledge from project-specific constraints, the system explicitly supports distinct entry types. It formats natural-language intent into either structured spec entries or learning entries, keeping reusable knowledge and project constraints logically apart.

Yes, this approach supports quality and testing rule capture for backend development. You can naturally state requirements like requiring eighty percent test coverage, and it will infer the quality category and apply the correct scope to the spec entry.