musubi-sdd 5.0.0 → 5.6.1

package/src/templates/agents/claude-code/skills/release-coordinator/feature-flag-guide.md

@@ -52,19 +52,19 @@ interface FeatureFlag {
 
 function isFeatureEnabled(flag: FeatureFlag, user: User): boolean {
   if (!flag.enabled) return false;
-  
+
   // Check user allowlist
   if (flag.allowedUsers?.includes(user.id)) return true;
-  
+
   // Check role allowlist
   if (flag.allowedRoles?.some(role => user.roles.includes(role))) return true;
-  
+
   // Check percentage rollout
   if (flag.percentage !== undefined) {
     const hash = hashUserId(user.id);
     return hash % 100 < flag.percentage;
   }
-  
+
   return flag.enabled;
 }
 ```
@@ -142,14 +142,14 @@ const currentFlags = flags[process.env.NODE_ENV];
 
 ```typescript
 // Good: Clear, descriptive names
-'enable-new-checkout-v2'
-'show-dark-mode-toggle'
-'use-graphql-api'
+'enable-new-checkout-v2';
+'show-dark-mode-toggle';
+'use-graphql-api';
 
 // Bad: Vague or cryptic
-'flag1'
-'test'
-'temp'
+'flag1';
+'test';
+'temp';
 ```
 
 ### 2. Default to Off
@@ -165,7 +165,7 @@ function getFlag(name: string): boolean {
 ```typescript
 /**
  * Feature Flag: new-payment-provider
- * 
+ *
  * Purpose: Enable new Stripe payment integration
  * Owner: payments-team
  * Created: 2024-01-15
@@ -192,7 +192,7 @@ describe('Checkout', () => {
     setFlag('new-checkout', true);
     // test new checkout
   });
-  
+
   it('works with new checkout disabled', () => {
     setFlag('new-checkout', false);
     // test legacy checkout
@@ -207,11 +207,11 @@ describe('Checkout', () => {
 ```typescript
 class FeatureFlagService {
   private flags: Map<string, FeatureFlag> = new Map();
-  
+
   constructor(private config: FlagConfig) {
     this.loadFlags();
   }
-  
+
   async loadFlags(): Promise<void> {
     // Load from remote config
     const response = await fetch('/api/flags');
@@ -220,13 +220,13 @@ class FeatureFlagService {
       this.flags.set(flag.name, flag);
     });
   }
-  
+
   isEnabled(name: string, context?: FlagContext): boolean {
     const flag = this.flags.get(name);
     if (!flag) return false;
     return evaluateFlag(flag, context);
   }
-  
+
   getAllFlags(): FeatureFlag[] {
     return Array.from(this.flags.values());
   }
@@ -243,7 +243,7 @@ const FeatureFlagContext = createContext<FeatureFlagService>(null);
 
 export function FeatureFlagProvider({ children }) {
   const flagService = useMemo(() => new FeatureFlagService(), []);
-  
+
   return (
     <FeatureFlagContext.Provider value={flagService}>
       {children}
@@ -255,18 +255,18 @@ export function FeatureFlagProvider({ children }) {
 export function useFeatureFlag(name: string): boolean {
   const flagService = useContext(FeatureFlagContext);
   const [enabled, setEnabled] = useState(false);
-  
+
   useEffect(() => {
     setEnabled(flagService.isEnabled(name));
   }, [name, flagService]);
-  
+
   return enabled;
 }
 
 // Component usage
 function MyComponent() {
   const showNewUI = useFeatureFlag('new-ui');
-  
+
   return showNewUI ? <NewUI /> : <LegacyUI />;
 }
 ```
@@ -275,17 +275,18 @@ function MyComponent() {
 
 ## Flag Audit Checklist
 
-| Flag Name | Owner | Created | Status | Cleanup Date |
-|-----------|-------|---------|--------|--------------|
-| new-checkout | @alice | 2024-01 | Active | - |
-| dark-mode | @bob | 2024-02 | Sunset | 2024-04-01 |
-| old-api | @carol | 2023-06 | Remove | Overdue! |
+| Flag Name    | Owner  | Created | Status | Cleanup Date |
+| ------------ | ------ | ------- | ------ | ------------ |
+| new-checkout | @alice | 2024-01 | Active | -            |
+| dark-mode    | @bob   | 2024-02 | Sunset | 2024-04-01   |
+| old-api      | @carol | 2023-06 | Remove | Overdue!     |
 
 ---
 
 ## Anti-Patterns
 
 ### ❌ Too Many Flags
+
 ```typescript
 // Bad: Feature flag soup
 if (flagA && flagB && !flagC && (flagD || flagE)) {
@@ -294,14 +295,17 @@ if (flagA && flagB && !flagC && (flagD || flagE)) {
 ```
 
 ### ❌ Permanent Flags
+
 ```typescript
 // Bad: Flag that's been on for 2 years
-if (flags.newLoginPage) { // Added in 2022
+if (flags.newLoginPage) {
+  // Added in 2022
   // This should just be the code now
 }
 ```
 
 ### ❌ Complex Flag Logic
+
 ```typescript
 // Bad: Flag with side effects
 if (flags.experimentX) {

package/src/templates/agents/claude-code/skills/release-coordinator/release-plan-template.md

@@ -13,22 +13,24 @@ Template for planning and executing software releases.
 
 ## Release Information
 
-| Field | Value |
-|-------|-------|
-| Version | v[X.Y.Z] |
-| Codename | [Optional] |
-| Release Date | YYYY-MM-DD |
-| Release Manager | [Name] |
-| Status | Planning / Ready / Released |
+| Field           | Value                       |
+| --------------- | --------------------------- |
+| Version         | v[X.Y.Z]                    |
+| Codename        | [Optional]                  |
+| Release Date    | YYYY-MM-DD                  |
+| Release Manager | [Name]                      |
+| Status          | Planning / Ready / Released |
 
 ---
 
 ## 1. Release Summary
 
 ### Highlights
+
 [Brief summary of major changes in this release]
 
 ### Release Type
+
 - [ ] Major (breaking changes)
 - [ ] Minor (new features, backwards compatible)
 - [ ] Patch (bug fixes only)
@@ -38,32 +40,37 @@ Template for planning and executing software releases.
 ## 2. Features & Changes
 
 ### New Features
-| ID | Feature | Owner | Status |
-|----|---------|-------|--------|
+
+| ID       | Feature       | Owner  | Status  |
+| -------- | ------------- | ------ | ------- |
 | FEAT-001 | [Description] | [Name] | ✅ Done |
 | FEAT-002 | [Description] | [Name] | ✅ Done |
 
 ### Bug Fixes
-| ID | Description | Severity | Status |
-|----|-------------|----------|--------|
-| BUG-001 | [Description] | High | ✅ Fixed |
-| BUG-002 | [Description] | Medium | ✅ Fixed |
+
+| ID      | Description   | Severity | Status   |
+| ------- | ------------- | -------- | -------- |
+| BUG-001 | [Description] | High     | ✅ Fixed |
+| BUG-002 | [Description] | Medium   | ✅ Fixed |
 
 ### Breaking Changes
-| Change | Migration Path |
-|--------|----------------|
+
+| Change                     | Migration Path   |
+| -------------------------- | ---------------- |
 | [Describe breaking change] | [How to migrate] |
 
 ### Deprecations
-| Feature | Deprecated In | Remove In |
-|---------|---------------|-----------|
-| [Feature] | v[X.Y.Z] | v[X+1.0.0] |
+
+| Feature   | Deprecated In | Remove In  |
+| --------- | ------------- | ---------- |
+| [Feature] | v[X.Y.Z]      | v[X+1.0.0] |
 
 ---
 
 ## 3. Quality Checklist
 
 ### Testing
+
 - [ ] All unit tests passing
 - [ ] Integration tests passing
 - [ ] E2E tests passing
@@ -71,12 +78,14 @@ Template for planning and executing software releases.
 - [ ] Security scan completed
 
 ### Documentation
+
 - [ ] README updated
 - [ ] API docs updated
 - [ ] CHANGELOG updated
 - [ ] Migration guide (if breaking)
 
 ### Review
+
 - [ ] Code review completed
 - [ ] Security review completed
 - [ ] Product owner sign-off
@@ -86,13 +95,15 @@ Template for planning and executing software releases.
 ## 4. Deployment Plan
 
 ### Pre-Release Tasks
-| Task | Owner | Due Date | Status |
-|------|-------|----------|--------|
-| Freeze feature branch | [Name] | MM/DD | ⬜ |
-| Create release branch | [Name] | MM/DD | ⬜ |
-| Final QA testing | [Name] | MM/DD | ⬜ |
+
+| Task                  | Owner  | Due Date | Status |
+| --------------------- | ------ | -------- | ------ |
+| Freeze feature branch | [Name] | MM/DD    | ⬜     |
+| Create release branch | [Name] | MM/DD    | ⬜     |
+| Final QA testing      | [Name] | MM/DD    | ⬜     |
 
 ### Deployment Steps
+
 1. [ ] Create Git tag
 2. [ ] Build release artifacts
 3. [ ] Deploy to staging
@@ -102,12 +113,15 @@ Template for planning and executing software releases.
 7. [ ] Announce release
 
 ### Rollback Plan
+
 **Trigger conditions**:
+
 - Error rate > 1%
 - P1 bug discovered
 - Performance degradation > 20%
 
 **Rollback steps**:
+
 1. Revert to previous version
 2. Notify stakeholders
 3. Create incident ticket
@@ -117,29 +131,33 @@ Template for planning and executing software releases.
 ## 5. Communication
 
 ### Internal
-| Audience | Channel | When |
-|----------|---------|------|
+
+| Audience    | Channel         | When           |
+| ----------- | --------------- | -------------- |
 | Engineering | Slack #releases | Day of release |
-| Support | Email | Day of release |
-| All Hands | Meeting | Next all-hands |
+| Support     | Email           | Day of release |
+| All Hands   | Meeting         | Next all-hands |
 
 ### External
-| Audience | Channel | When |
-|----------|---------|------|
-| Users | Release Notes | Day of release |
-| Blog | Blog Post | Day of release |
-| Social | Twitter | Day of release |
+
+| Audience | Channel       | When           |
+| -------- | ------------- | -------------- |
+| Users    | Release Notes | Day of release |
+| Blog     | Blog Post     | Day of release |
+| Social   | Twitter       | Day of release |
 
 ---
 
 ## 6. Post-Release
 
 ### Monitoring
+
 - [ ] Error rates monitored for 24h
 - [ ] Performance metrics tracked
 - [ ] User feedback collected
 
 ### Follow-up
+
 - [ ] Retro scheduled
 - [ ] Metrics reviewed
 - [ ] Lessons documented
@@ -149,12 +167,14 @@ Template for planning and executing software releases.
 ## Appendix
 
 ### A. Version History
-| Version | Date | Notes |
-|---------|------|-------|
-| v[X.Y.Z] | MM/DD | Current release |
+
+| Version    | Date  | Notes            |
+| ---------- | ----- | ---------------- |
+| v[X.Y.Z]   | MM/DD | Current release  |
 | v[X.Y.Z-1] | MM/DD | Previous release |
 
 ### B. Related Links
+
 - [Release Branch]
 - [Test Reports]
 - [CHANGELOG]
@@ -165,24 +185,28 @@ Template for planning and executing software releases.
 ## Release Checklist
 
 ### 1 Week Before
+
 - [ ] Feature freeze
 - [ ] Create release branch
 - [ ] Update version number
 - [ ] Begin final testing
 
 ### 1 Day Before
+
 - [ ] All tests passing
 - [ ] Documentation complete
 - [ ] CHANGELOG finalized
 - [ ] Stakeholder sign-off
 
 ### Release Day
+
 - [ ] Create Git tag
 - [ ] Build and publish
 - [ ] Deploy to production
 - [ ] Announce release
 
 ### 1 Day After
+
 - [ ] Monitor metrics
 - [ ] Address urgent issues
 - [ ] Collect feedback
@@ -202,29 +226,37 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
 ## [Unreleased]
 
 ### Added
+
 - New features
 
 ### Changed
+
 - Changes in existing functionality
 
 ### Deprecated
+
 - Features to be removed in future
 
 ### Removed
+
 - Removed features
 
 ### Fixed
+
 - Bug fixes
 
 ### Security
+
 - Security improvements
 
 ## [X.Y.Z] - YYYY-MM-DD
 
 ### Added
+
 - Feature A (#123)
 - Feature B (#124)
 
 ### Fixed
+
 - Bug C (#125)
 ```

package/src/templates/agents/claude-code/skills/requirements-analyst/ears-format.md

@@ -15,6 +15,7 @@ EARS is a structured syntax for writing unambiguous, testable requirements. All
 **Use When**: Requirement applies at all times, unconditionally.
 
 **Examples**:
+
 ```markdown
 REQ-001: The system SHALL encrypt all passwords using bcrypt with minimum 12 rounds.
 REQ-002: The API SHALL return responses in JSON format.
@@ -30,6 +31,7 @@ REQ-003: The application SHALL log all authentication attempts.
 **Use When**: Requirement is triggered by a specific event or user action.
 
 **Examples**:
+
 ```markdown
 REQ-010: WHEN user submits login form, the system SHALL validate credentials within 2 seconds.
 REQ-011: WHEN payment is processed, the system SHALL send confirmation email.
@@ -46,6 +48,7 @@ REQ-013: WHEN session expires, the system SHALL redirect user to login page.
 **Use When**: Requirement applies during a specific system state or condition.
 
 **Examples**:
+
 ```markdown
 REQ-020: WHILE user is authenticated, the system SHALL display user dashboard.
 REQ-021: WHILE database connection is lost, the system SHALL queue write operations.
@@ -62,6 +65,7 @@ REQ-023: WHILE rate limit is exceeded, the system SHALL return 429 status.
 **Use When**: Requirement depends on optional feature being enabled.
 
 **Examples**:
+
 ```markdown
 REQ-030: WHERE two-factor authentication is enabled, the system SHALL require OTP after password.
 REQ-031: WHERE dark mode is selected, the system SHALL apply dark theme CSS.
@@ -78,6 +82,7 @@ REQ-033: WHERE email notifications are enabled, the system SHALL send daily dige
 **Use When**: Defining how system should handle errors, exceptions, or edge cases.
 
 **Examples**:
+
 ```markdown
 REQ-040: IF login fails 5 times, THEN the system SHALL lock account for 30 minutes.
 REQ-041: IF payment gateway timeout occurs, THEN the system SHALL retry 3 times.
@@ -92,15 +97,16 @@ REQ-043: IF disk space is below 10%, THEN the system SHALL alert administrators.
 **Template**: Combine patterns for complex scenarios.
 
 **Examples**:
+
 ```markdown
-REQ-050: WHILE user is authenticated, WHEN session is about to expire, 
-         the system SHALL display warning 5 minutes before expiration.
+REQ-050: WHILE user is authenticated, WHEN session is about to expire,
+the system SHALL display warning 5 minutes before expiration.
 
-REQ-051: WHERE premium subscription is active, WHEN user uploads file, 
-         the system SHALL allow files up to 100MB.
+REQ-051: WHERE premium subscription is active, WHEN user uploads file,
+the system SHALL allow files up to 100MB.
 
-REQ-052: IF payment fails, THEN WHILE retry count < 3, 
-         the system SHALL attempt payment again after 30 seconds.
+REQ-052: IF payment fails, THEN WHILE retry count < 3,
+the system SHALL attempt payment again after 30 seconds.
 ```
 
 ---
@@ -109,26 +115,27 @@ REQ-052: IF payment fails, THEN WHILE retry count < 3,
 
 ### Required Keywords (SHALL/MUST)
 
-| Keyword | Meaning | Use |
-|---------|---------|-----|
-| **SHALL** | Mandatory requirement | Primary choice |
-| **MUST** | Mandatory requirement | Alternative to SHALL |
+| Keyword   | Meaning               | Use                  |
+| --------- | --------------------- | -------------------- |
+| **SHALL** | Mandatory requirement | Primary choice       |
+| **MUST**  | Mandatory requirement | Alternative to SHALL |
 
 ### Forbidden Keywords (Ambiguous)
 
-| Keyword | Problem | Replace With |
-|---------|---------|--------------|
-| should | Ambiguous obligation | SHALL |
-| may | Unclear optionality | WHERE + SHALL |
-| could | Vague possibility | SHALL or remove |
-| might | Uncertain behavior | SHALL or remove |
-| would | Conditional ambiguity | SHALL |
+| Keyword | Problem               | Replace With    |
+| ------- | --------------------- | --------------- |
+| should  | Ambiguous obligation  | SHALL           |
+| may     | Unclear optionality   | WHERE + SHALL   |
+| could   | Vague possibility     | SHALL or remove |
+| might   | Uncertain behavior    | SHALL or remove |
+| would   | Conditional ambiguity | SHALL           |
 
 ---
 
 ## Requirement ID Format
 
 ### Standard Format
+
 ```
 REQ-[Category]-[Number]
 
@@ -141,43 +148,47 @@ REQ-NF-001    # Non-functional requirement
 
 ### Categories
 
-| Category | Description |
-|----------|-------------|
-| AUTH | Authentication & Authorization |
-| USER | User Management |
-| PAY | Payment & Billing |
-| UI | User Interface |
-| API | API & Integration |
-| DATA | Data Management |
-| SEC | Security |
-| PERF | Performance |
-| NF | Non-Functional |
+| Category | Description                    |
+| -------- | ------------------------------ |
+| AUTH     | Authentication & Authorization |
+| USER     | User Management                |
+| PAY      | Payment & Billing              |
+| UI       | User Interface                 |
+| API      | API & Integration              |
+| DATA     | Data Management                |
+| SEC      | Security                       |
+| PERF     | Performance                    |
+| NF       | Non-Functional                 |
 
 ---
 
 ## Validation Rules
 
 ### Rule 1: One Requirement Per Statement
+
 ```
 ❌ BAD: The system SHALL validate credentials AND send welcome email.
-✅ GOOD: 
+✅ GOOD:
   REQ-001: The system SHALL validate credentials.
   REQ-002: WHEN login succeeds, the system SHALL send welcome email.
 ```
 
 ### Rule 2: Measurable Actions
+
 ```
 ❌ BAD: The system SHALL be fast.
 ✅ GOOD: The system SHALL respond within 200ms for 95% of requests.
 ```
 
 ### Rule 3: No Implementation Details
+
 ```
 ❌ BAD: The system SHALL use Redis for caching.
 ✅ GOOD: The system SHALL cache frequently accessed data.
 ```
 
 ### Rule 4: Testable Conditions
+
 ```
 ❌ BAD: WHEN user is unhappy, the system SHALL improve experience.
 ✅ GOOD: WHEN user rating is below 3, the system SHALL prompt for feedback.
@@ -191,6 +202,7 @@ REQ-NF-001    # Non-functional requirement
 # Requirements Specification: [Feature Name]
 
 ## Document Information
+
 - **Version**: 1.0
 - **Date**: YYYY-MM-DD
 - **Author**: requirements-analyst
@@ -200,21 +212,21 @@ REQ-NF-001    # Non-functional requirement
 
 ### 1.1 Authentication
 
-REQ-AUTH-001: WHEN user submits login form with valid credentials, 
-              the system SHALL authenticate user and create session.
+REQ-AUTH-001: WHEN user submits login form with valid credentials,
+the system SHALL authenticate user and create session.
 
-REQ-AUTH-002: IF login credentials are invalid, 
-              THEN the system SHALL display error message.
+REQ-AUTH-002: IF login credentials are invalid,
+THEN the system SHALL display error message.
 
-REQ-AUTH-003: IF login fails 5 consecutive times, 
-              THEN the system SHALL lock account for 30 minutes.
+REQ-AUTH-003: IF login fails 5 consecutive times,
+THEN the system SHALL lock account for 30 minutes.
 
 ### 1.2 User Management
 
 REQ-USER-001: The system SHALL store user profiles with name, email, and avatar.
 
-REQ-USER-002: WHEN user updates profile, 
-              the system SHALL validate and save changes.
+REQ-USER-002: WHEN user updates profile,
+the system SHALL validate and save changes.
 
 ## 2. Non-Functional Requirements
 
@@ -236,11 +248,11 @@ REQ-NF-005: The system SHALL maintain 99.9% uptime.
 
 ## 3. Traceability
 
-| REQ ID | Design Component | Priority | Status |
-|--------|------------------|----------|--------|
-| REQ-AUTH-001 | Auth Service | P1 | Approved |
-| REQ-AUTH-002 | Auth Service | P1 | Approved |
-| REQ-USER-001 | User Service | P2 | Draft |
+| REQ ID       | Design Component | Priority | Status   |
+| ------------ | ---------------- | -------- | -------- |
+| REQ-AUTH-001 | Auth Service     | P1       | Approved |
+| REQ-AUTH-002 | Auth Service     | P1       | Approved |
+| REQ-USER-001 | User Service     | P2       | Draft    |
 ```
 
 ---