Provides guidelines for feature specification, PRD writing, scope management, feature prioritization, stakeholder alignment, and change requests with 42 prioritized rules to prevent scope creep.
npx claudepluginhub joshuarweaver/cascade-code-general-misc-1 --plugin pproenca-dot-skills-1This skill uses the workspace's default tool permissions.
Comprehensive feature specification and planning guide for software engineers, product managers, and technical leads. Contains 42 rules across 8 categories, prioritized by impact to prevent scope creep and ensure project success.
Applies Acme Corporation brand guidelines including colors, fonts, layouts, and messaging to generated PowerPoint, Excel, and PDF documents.
Builds DCF models with sensitivity analysis, Monte Carlo simulations, and scenario planning for investment valuation and risk assessment.
Calculates profitability (ROE, margins), liquidity (current ratio), leverage, efficiency, and valuation (P/E, EV/EBITDA) ratios from financial statements in CSV, JSON, text, or Excel for investment analysis.
Comprehensive feature specification and planning guide for software engineers, product managers, and technical leads. Contains 42 rules across 8 categories, prioritized by impact to prevent scope creep and ensure project success.
Reference these guidelines when:
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Scope Definition | CRITICAL | scope- |
| 2 | Requirements Clarity | CRITICAL | req- |
| 3 | Prioritization Frameworks | HIGH | prio- |
| 4 | Acceptance Criteria | HIGH | accept- |
| 5 | Stakeholder Alignment | MEDIUM-HIGH | stake- |
| 6 | Technical Specification | MEDIUM | tech- |
| 7 | Change Management | MEDIUM | change- |
| 8 | Documentation Standards | LOW | doc- |
scope-define-boundaries - Define explicit scope boundariesscope-document-assumptions - Document all assumptions explicitlyscope-work-breakdown - Break scope into measurable work itemsscope-define-mvp - Define MVP before full feature setscope-stakeholder-signoff - Get stakeholder signoff on scopereq-specific-measurable - Write specific, measurable requirementsreq-user-stories - Structure requirements as user storiesreq-avoid-solution-language - Avoid solution-specific languagereq-functional-nonfunctional - Separate functional and non-functionalreq-consistent-terminology - Use consistent terminologyreq-traceability - Maintain requirements traceabilityprio-moscow-method - Use MoSCoW prioritization methodprio-rice-scoring - Apply RICE scoring for objectivityprio-value-vs-effort - Map value vs effort explicitlyprio-dependencies-first - Identify and order dependenciesprio-kano-model - Apply Kano model for feature classificationaccept-given-when-then - Use Given-When-Then formataccept-testable-criteria - Write testable acceptance criteriaaccept-edge-cases - Include edge cases in acceptanceaccept-definition-of-done - Define clear definition of doneaccept-avoid-over-specification - Avoid over-specificationstake-identify-stakeholders - Identify all stakeholders earlystake-early-feedback - Gather feedback early and oftenstake-conflict-resolution - Resolve conflicts explicitlystake-communication-plan - Establish communication cadencestake-success-metrics - Align on success metricstech-system-context - Document system context and dependenciestech-api-contracts - Define API contracts before implementationtech-data-model - Specify data models and schema changestech-error-handling - Plan error handling and recoverytech-performance-requirements - Specify performance requirementstech-security-considerations - Document security considerationschange-formal-process - Use formal change request processchange-impact-assessment - Assess full impact before approvalchange-version-tracking - Version all specification documentschange-scope-freeze - Implement scope freeze periodschange-defer-log - Maintain deferred items logdoc-single-source - Maintain single source of truthdoc-consistent-templates - Use consistent document templatesdoc-decision-records - Document key decisions with contextdoc-accessible-format - Keep documentation accessibledoc-glossary-terms - Define project terminology